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
Most recently taken up by
- rivet-dev/rivetkitword for word, first seen Oct 9, 2026
- rivet-dev/agent-osword for word, first seen Oct 8, 2026
Who's talking about rivet-dev/agentos
- @rusttrending.bsky.social“rivet-dev / agentos: A faster, lighter, cheaper alternative to sandboxes. Run any coding agent inside an …”Bluesky · Jun 27, 2026 · 1 likes
- @github-trending-rs.bsky.social“📦 rivet-dev / agentos ⭐ 3,278 (+52) 🗒 Rust A faster, lighter, cheaper alternative to sandboxes. Run any …”Bluesky · Jun 27, 2026 · 1 likes
- swcstudiospace/realm“build(deps): bump @rivet-dev/agentos-core from 0.4.4 to 0.4.6”GitHub · Nov 5, 2026
- greyhaven-ai/autocontext“chore(deps): bump the typescript-versions group in /ts with 13 updates”GitHub · Oct 23, 2026
- joshyorko/actions“research: test disposable V8/WASM Code Mode against existing Actions data and execution contracts”GitHub · Oct 15, 2026
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
- Nov 5, 2026build(deps): bump @rivet-dev/agentos-core from 0.4.4 to 0.4.6 — swcstudiospace/realm0 reactions
- Oct 23, 2026chore(deps): bump the typescript-versions group in /ts with 13 updates — greyhaven-ai/autocontext0 reactions
- Oct 15, 2026research: test disposable V8/WASM Code Mode against existing Actions data and execution contracts — joshyorko/actions0 reactions
- Sep 7, 2026fix(post): cite rivet-dev/agentos for POST-20260907-000160 — Interchouette/itcy-publications0 reactions
- Jul 29, 2026Secure tool execution, good choice to manage what agent can do — kanthorlabs/kanthord0 reactions
1 more on GitHub
- Jul 8, 2026Sandboxing — P0u4a/nova0 reactions
On Bluesky · 2
- Jun 27, 2026rivet-dev / agentos: A faster, lighter, cheaper alternative to sandboxes. Run any coding agent inside an isolated Linux VM, with agent… — @rusttrending.bsky.social1 likes and repost
- Jun 27, 2026📦 rivet-dev / agentos ⭐ 3,278 (+52) 🗒 Rust A faster, lighter, cheaper alternative to sandboxes. Run any coding agent inside an isolated… — @github-trending-rs.bsky.social1 likes and repost
Other versions2 projects use a version of this.
Word for word · 2
- rivet-dev/agent-os★ 4.9k100% same
- 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.
- CLAUDE.mdCLAUDE.md
- crates/CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- launch-graphicsSkill
- publish-registrySkill
- release-previewSkill
- releaseSkill
- sanity-checkSkill
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
- Very specific: line 20
Never setState from a useEffect to derive state from props, query data, or other state.
≈ “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.
Files
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
AgentOsfacade 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, orpip. Add typed, injection-safe helpers for stable intents, not one method per CLI flag; keepexec,execArgv, andspawnas 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
setStatefrom auseEffectto 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-rollbusy/errorstate around anasynchandler. - Coupled state that always changes together belongs in one
useReducer(or one state object), not in a pile of independentuseStatecalls updated in sequence. - Imperative browser resources (object URLs, observers, listeners) belong in a self-contained hook that owns both creation and cleanup.
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
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.

