Rivet Launches the Sandbox Agent SDK to Solve Agent API Fragmentation
Briefly

Rivet Launches the Sandbox Agent SDK to Solve Agent API Fragmentation
"Rivet Sandbox Agent SDK provides a universal API for coding agents, allowing developers to work with different agent runtimes like Claude Code, Codex, OpenCode, and Amp without rewriting their integration for each one. It addresses the fragmentation across agent APIs, session handling, and streaming formats that has historically made agent integrations complex and difficult to maintain. According to Rivet co-founder and CTO Nathan Flurry, the difficulty of building agentic systems comes down to three core challenges: API fragmentation, transient state, and deployment variance across providers."
"Building coding agents is hard. Claude Code has one API. Codex has another. OpenCode and Amp each do things differently. And even if you picked one, you'd face session state disappearing when processes crash, different integration code for every sandbox provider, and no way to stream transcripts back to your application. Each agent comes with its own event format, session model, and permission system."
"In contrast, Rivet's Sandbox Agent SDK offers the possibility of writing one integration against a unified API and swap agents with just a configuration change. Here's a minimal example of how to create an agent session using the SDK: import { SandboxAgent } from "sandbox-agent"; const client = await SandboxAgent.start(); await client.createSession("my-session", { agent: "claude", // or "codex", "opencode", "amp" permissionMode: "auto", }); for await (const event of client.streamEvents("my-session")) { console.log(event.type, event.data); }"
Rivet Sandbox Agent SDK provides a universal API for coding agents, enabling developers to use runtimes such as Claude Code, Codex, OpenCode, and Amp without rewriting integrations. The SDK resolves fragmentation across agent APIs, session handling, and streaming formats that complicate maintenance. Three core challenges for agentic systems are API fragmentation, transient state, and deployment variance across providers. Agents differ in event formats, session models, and permission systems—Claude Code uses JSONL over stdout while Codex uses JSON-RPC—requiring separate integrations. Platform-specific deployment APIs add more variance. The SDK offers a unified session schema, event streaming, and the ability to swap agents via configuration.
Read at InfoQ
Unable to calculate read time
[
|
]