Rivet releases agentOS v0.2.0 with WebAssembly sandboxing and 1738x cheaper claim
Rivet released agentOS v0.2.0, a Rust rewrite of its WebAssembly-based sandbox and orchestration stack with multiplayer workflows and one-prompt deployment. The release targets self-hosted and cloud agent runtimes, and Rivet claims 1738x lower cost than SaaS sandboxes.

TL;DR
- rivet_dev's launch thread introduced agentOS v0.2.0 as a WebAssembly-based sandbox and orchestration stack, with support for "any agent" including Pi, Claude Code, Codex, and OpenCode.
- According to rivet_dev's launch thread, the new release is a Rust rewrite and carries Rivet's headline claim of being 1738x cheaper than SaaS sandboxes.
- rivet_dev's launch thread also positioned v0.2.0 around multiplayer workflows, agent-to-agent coordination, and one-prompt deployment to Rivet Cloud or self-hosted environments.
- The linked rivet_dev's GitHub post, rivet_dev's documentation post, and rivet_dev's read-more post suggest this was shipped as a full stack update, not just a pricing tweak.
You can jump straight from rivet_dev's GitHub link to the code, rivet_dev's documentation link to the docs, and rivet_dev's read-more link to the broader write-up. The oddest detail is how hard Rivet leaned into cost as a product feature: the launch pairs WebAssembly sandboxing with a precise "1738x cheaper" number in the main announcement, then bundles that with multiplayer and agent-agent orchestration instead of pitching sandboxing as a narrow infra primitive.
What shipped
Rivet framed agentOS v0.2.0 as four concrete pieces in one release:
- WebAssembly-powered lightweight sandboxing
- Agent orchestration for first-party or bring-your-own agents
- Multiplayer workflows and agent-agent coordination
- One-prompt deployment to Rivet Cloud or self-hosted targets
The same launch thread also says the system was rewritten in Rust, which makes this look more like a runtime reset than a point upgrade.
Code and docs surfaces
Rivet split the release trail across three official surfaces:
- GitHub for the codebase
- Documentation for setup and product docs
- Read more for the broader release context
That matters mostly because the launch thread is short. The companion links imply agentOS is meant to be inspected, deployed, and self-hosted, not just tried as a hosted demo.
The cost claim
The strongest marketing line in the release is still the cheapest one: rivet_dev's main announcement says agentOS is 1738x cheaper than SaaS sandboxes.
The tweet evidence does not break down the benchmark, workload, or comparison set behind that number. What it does show is Rivet tying the economics claim directly to its WebAssembly sandbox design and to self-hosted deployment, instead of treating cost as a side note.
Skills and memory workflows
Moritz Kremb's coaching recap adds a more user-level picture of how AgentOS is being used. His list names cross-session memory, a tools doc, skills files, routines and triggers, and an automation layer that turns step-by-step skills into recurring runs.
That same post also describes one concrete workflow, pulling a Fathom call transcript into Notion, plus a custom clip pipeline using Tokscript and FFmpeg. Those details are not in Rivet's launch copy, but they make the product shape clearer: agentOS is being pitched as both a sandbox runtime and a filesystem-style automation harness.