rivet-dev / sandbox-agent

Sandbox Agent is a Rust server that runs inside a sandbox (E2B, Daytona, Modal, Docker, or your own infrastructure) and exposes coding agents — Claude Code, Codex, OpenCode, Cursor, Amp, Pi — over one HTTP/SSE API, so a client application can create a session, stream its events in a normalized schema, and swap between agents without rewriting the integration. A TypeScript SDK, a CLI, and a built-in Inspector UI cover local embedded use as well as the remote server mode.

The sandbox-agent skill matches that: it covers deploying the server, creating and managing sessions through the SDK or API, and streaming agent events. agent-browser is a separate browser-automation CLI — navigating pages, filling forms, taking screenshots — with no connection to sandboxed coding agents; and random-number does exactly what its name says, generating an integer between two bounds. Both read as if they came along from elsewhere in the same organization's skill set rather than being written for this package.

READ THE FULL ANALYSIS＋

Who this is for. Someone building a product that lets an AI agent write and run code remotely, who needs isolation and one API across several agent CLIs instead of a separate integration per agent. If you came for browser automation or a random-number utility, treat those two as unrelated bonus skills, not evidence about Sandbox Agent.

What it costs to start. The sandbox-agent skill needs the Rust binary installed inside whatever sandbox you use — one curl command — plus, in production, your own storage for the streamed session events, since Sandbox Agent does not persist them itself. agent-browser and random-number both run with nothing extra installed.