agentleFS
rivet-devrivet-dev/agentos/packages/CLAUDE.md

agentos / packages

CLAUDE.md4.9k starsChanged 45 days agoApache-2.0View on GitHub

- Client packages must stay same-version with the sidecar: assert the single protocol version integer, and do not add wire back-compat, runtime negotiation, or converters. - Generated client layers return raw generated protocol types. The embedded AgentOs facade is publicly exported from @rivet-dev/agentos-core. - Generic agentos clients must stay application-agnostic and forward only the sandbox protocol. - agentos packages must never depend on agent-os packages; dependency direction is strictly agent-os to agentos and must be CI-enforced after the split. -…

2 other projects use a version of this.

Trending

Steady talk.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 2 mentionsJul 2026: 2 mentionsAug 2026: 0 mentionsSep 2026: 1 mentionOct 2026: 2 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the rivet-dev/agentos repository that our weekly crawl found: only 8 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about rivet-dev/agentos

The biggest 5 of 8 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 8

Talked about on GitHub and Bluesky (8 times).

On GitHub · 6

1 more on GitHub
  • Other versions2 projects use a version of this.

    Word for word · 2

    1. rivet-dev/agent-os★ 4.9k100% same
    2. rivet-dev/rivetkit★ 4.9k100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository8 other files it gives its agents.

The file

We split this CLAUDE.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Never setState from a useEffect to derive state from props, query data, or other state.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

agentOS Packages

  • Client packages must stay same-version with the sidecar: assert the single protocol version integer, and do not add wire back-compat, runtime negotiation, or converters.
  • Generated client layers return raw generated protocol types. The embedded AgentOs facade is publicly exported from @rivet-dev/agentos-core.
  • Generic agentos clients must stay application-agnostic and forward only the sandbox protocol.
  • agentos packages must never depend on agent-os packages; dependency direction is strictly agent-os to agentos and must be CI-enforced after the split.
  • The sidecar remains the source of truth for runtime behavior; TypeScript package code should forward generated requests instead of reimplementing sidecar state machines.
  • Language modules own their ecosystem's common end-to-end workflows: source and file execution, value evaluation, dependency installation, project entry points, and standard module/script workflows must not require users to invoke node, python, python -m, npm, or pip. Add typed, injection-safe helpers for stable intents, not one method per CLI flag; keep exec, execArgv, and spawn as the uncommon-command escape hatch.
  • Cron and VM configuration types are Rust-owned after the split; TypeScript packages may re-export or mirror them only in lockstep.

React UI (dashboard inspector)

  • Never setState from a useEffect to derive state from props, query data, or other state. Derive it during render (useMemo), or reset it during render by comparing against the value it is keyed on. Effects are for subscriptions, timers, and imperative cleanup only.
  • Server mutations use useMutation; do not hand-roll busy/error state around an async handler.
  • Coupled state that always changes together belongs in one useReducer (or one state object), not in a pile of independent useState calls updated in sequence.
  • Imperative browser resources (object URLs, observers, listeners) belong in a self-contained hook that owns both creation and cleanup.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.