Index of every page on this site: llms.txt
All skills
rivet-dev avatar

/sandbox-agent

@3b027b3 official
by Rivetrivet-dev/skills53 stars
14
Run it yourself

Deploy, configure, and integrate Sandbox Agent - a universal API for orchestrating AI coding agents (Claude Code, Codex, OpenCode, Amp) in sandboxed environments. Use when setting up sandbox-agent server locally or in cloud sandboxes (E2B, Daytona, Docker), creating and managing agent sessions via SDK or API, streaming agent events and handling human-in-the-loop interactions, building chat UIs for coding agents, or understanding the universal schema for agent responses.

Use this Skill: https://skilld.dev/gh/rivet-dev/skills/sandbox-agent

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesdeployagentcomputer.md

≈493 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Agent Computer

Source: sandbox-agent/docs/content/docs/deploy/agentcomputer.mdx Canonical URL: https://rivet.dev/sandbox-agent/docs/deploy/agentcomputer Description: Run Sandbox Agent on Agent Computer managed workers.


Prerequisites

  • COMPUTER_API_KEY or AGENTCOMPUTER_API_KEY
  • An Agent Computer managed-worker image, or default machine source, that already has your coding agent authenticated

The platform image already includes Sandbox Agent, Claude Code, and Codex. Agent credentials still live inside the machine, so make sure your image or workspace bootstrap has already handled agent login.

TypeScript example

npm install sandbox-agent@0.5.x
import { SandboxAgent } from "sandbox-agent";
import { agentcomputer } from "sandbox-agent/agentcomputer";

const sdk = await SandboxAgent.start({
  sandbox: agentcomputer(),
});

try {
  const health = await sdk.getHealth();
  console.log(health.status);
  console.log(sdk.inspectorUrl);

  const agents = await sdk.listAgents();
  console.log(agents.agents.map((agent) => agent.id));
} finally {
  await sdk.destroySandbox();
}

The agentcomputer provider creates a managed-worker computer, waits until browser access is ready, and routes SDK requests through the machine's authenticated web host. sdk.inspectorUrl is already a browser-ready URL, so it opens the built-in Inspector directly.

By default, the provider creates:

  • runtimeFamily: "managed-worker"
  • usePlatformDefault: true

Pass create when you want to override the handle, workspace name, or other machine-create settings:

const sdk = await SandboxAgent.start({
  sandbox: agentcomputer({
    create: {
      handle: "sandbox-agent-demo",
      workspaceName: "sandbox-agent-demo",
      usePlatformDefault: false,
    },
  }),
});

Set apiUrl when you are targeting a self-hosted or local Agent Computer API instead of https://api.computer.agentcomputer.ai.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

3 alerts1d5 checks · Risk HIGH
  • Gen Agent Trust Hub1d

    The skill provides a universal API for orchestrating coding agents in sandboxed environments. It includes instructions for installing its own server components and various development tools using piped shell execution (remote code execution). The tool possesses broad capabilities for arbitrary command execution, filesystem access, and desktop control, and it features mechanisms for the agent to extract and export LLM credentials from the local host environment.

  • Socket1d

    1 alert: gptAnomaly

  • Snyk1d

    Risk: CRITICAL · 2 issues

  • Runlayer8mo

    34/41 files flagged

  • ZeroLeaks7mo

    1 finding · Score: 82/100

Signed by skilld at 3b027b3. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 days ago
  • TypeScript
  • sandbox-agent
  • api-orchestration
  • ai-agents
  • claude
  • openai
  • e2b
  • daytona
  • docker
  • session-management

README badge

README badge for rivet-dev/skills/sandbox-agent

Provides a universal API and orchestration layer for running Claude, Codex, OpenCode, and Amp coding agents in sandboxed environments (E2B, Daytona, Docker). Covers server setup, session management, event streaming, and integration with chat UIs and LLM providers.

Generated from the current SKILL.md.

Which coding agents does Sandbox Agent support?
Sandbox Agent provides a universal API for Claude Code, Codex, OpenCode, and Amp. It also supports a mock agent for testing without provider credentials.
What sandbox providers can I deploy to?
Sandbox Agent runs on E2B, Daytona, Docker, local development, and cloud platforms like Vercel and Cloudflare. You can also run it as a local subprocess via Node.js or Bun.
Do I need API keys to test Sandbox Agent?
No. Use the mock agent for SDK and integration testing without Anthropic or OpenAI credentials. For real agents, you'll need to set ANTHROPIC_API_KEY and/or OPENAI_API_KEY.
Can I use this for per-user billing or multi-tenant setups?
Yes. Sandbox Agent supports LLM credential gateways like OpenRouter, LiteLLM, and Portkey for per-tenant token tracking, budget enforcement, and usage-based billing.
What persistence options are available for agent sessions?
Sessions can be persisted in-memory, to Rivet Actor state, IndexedDB, SQLite, or Postgres depending on your deployment target.

Generated from the current SKILL.md. These answers refresh after source changes.