harivansh-afk/sandbox-agent
1
0
Fork 0
mirror of https://github.com/harivansh-afk/sandbox-agent.git synced 2026-04-15 05:02:11 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
sandbox-agent/README.md
Nathan Flurry a49ea094f3 refactor: rename sandbox-daemon to sandbox-agent
2026-01-25 02:30:12 -08:00

2.7 KiB
Raw Blame History

Sandbox Agent SDK

Run inside sandboxes to provide support

  • Any coding agent: Universal API to interact with all agents with full feature coverage
  • Server Mode: Run as HTTP server from any sandbox provider or as TypeScript & Python SDK
  • Universal session schema: Universal schema to store agent transcripts
  • Supports your sandbox provider: Daytona, E2B, Vercel Sandboxes, add your own
  • Lightweight, portable Rust binary: Install anywhere with 1 curl command
  • Compatible with Vercel AI SDK: TODO

Quickstart

Start with the SDK:

TODO

To run this in server mode, install with:

TODO

And run with:

TODO

See the example for your provider of choice:

Security

TODO: Tokens TODO: Using a gateawy TODO: BYO tokens with extractor

Demo Frontend

TODO: Screenshot

This project provides a demo frontend for testing the connection. Run it with:

TODO

Agent Compatibility Matrix

TODO

Reference

TypeScript SDK

TODO

HTTP API

TODO

CLI

TODO

FAQ

TODO

  • Why not use PTY? This is the recommended option for XXXX
  • Why not use ?
  • Does it support ?
  • Can I use this with my personal OpenAPI & Claude tokens?

Project Scope

This project aims to solve 3 problems with agents:

  • Universal Coding Agent API: Claude Code, Codex, Amp, and OpenCode all have put a lot of work in to the agent scaffold. Each have respective pros and cons and need to be easy to be swapped between.
  • Agents In Sandboxes: There are many complications with running agents inside of sandbox providers. This lets you run a simple curl command to spawn an HTTP server for using any agent from within the sandbox.
  • Agent Transcript: Maintaining agent transcripts is difficult since the agent manages its own sessions. This provides a simpler way to read and retrieve agent transcripts in your system.

Features out of scope:

  • Storage of sessions on disk: Sessions are already stored by the respective coding agents on disk. It's assumed that the consumer is streaming data from this machine to an extral storage, such as Postgres, ClickHouse, or Rivet.
  • Direct LLM wrappers: Use the Vercel AI SDK if you want to impelment your own agent from scratch
  • Git Repo Management: Just use git commands or the features provided by your sandbox provider of choice.
  • Sandbox Provider API: Sandbox providers have many nuanced differences in their API, it does not make sense for us to try to provide a custom layer. Instead, we opt to provide skills that lets you integrate this project with sandbox providers.