agentOS: An Operating System for Agents, as a Library
Everyone shipping agents to production rebuilds the same boring stack: code execution, file storage, orchestration, permissions, state that survives a restart. Rivet's agentOS collapses all of it into an import. Instead of spinning up a microVM or a sandbox per agent, each agent runs as an operating-system-as-a-library inside your existing backend process, on WebAssembly and V8 isolates.
The pitch is the economics. Rivet claims 92x faster cold starts, 47x less memory, and 254x cheaper than sandbox providers. If you've ever run an agent fleet, you know the sandbox bill and the cold-start latency are the two things that quietly cap how many agents you can afford to have running at once. Attacking that with WASM instead of full VMs is the right layer to attack.
What you get: built-in agents like Claude Code, Codex, OpenCode and Pi, JavaScript bindings so agents call host functions directly, granular filesystem/network/process permissions, execution for Bash, Node and Python, agent-to-agent orchestration, and session management over Agent Client Protocol. Apache 2.0, around 4,200 stars.
The bigger point is that agent infrastructure is quietly standardizing. A year ago every team wrote its own sandbox glue. Now the glue is becoming a dependency you add, and the interesting work moves up a layer to what the agents actually do. Repo at github.com/rivet-dev/agentos.
← Back to all articles
The pitch is the economics. Rivet claims 92x faster cold starts, 47x less memory, and 254x cheaper than sandbox providers. If you've ever run an agent fleet, you know the sandbox bill and the cold-start latency are the two things that quietly cap how many agents you can afford to have running at once. Attacking that with WASM instead of full VMs is the right layer to attack.
What you get: built-in agents like Claude Code, Codex, OpenCode and Pi, JavaScript bindings so agents call host functions directly, granular filesystem/network/process permissions, execution for Bash, Node and Python, agent-to-agent orchestration, and session management over Agent Client Protocol. Apache 2.0, around 4,200 stars.
The bigger point is that agent infrastructure is quietly standardizing. A year ago every team wrote its own sandbox glue. Now the glue is becoming a dependency you add, and the interesting work moves up a layer to what the agents actually do. Repo at github.com/rivet-dev/agentos.
Comments