Sandbox Adapter

Use one API to create and drive sandboxes on agentOS, E2B, Daytona, or Freestyle from any Rivet Actor, without the agent harness.

TODO

This page is not written yet. The outline below is what it will cover.

What this page will cover

• The four providers and the setup each one needs: agentOS with no account, and E2B, Daytona, and Freestyle with their SDKs and API keys.
• The Sandbox operations: exec, readFile, writeFile, mkdir, stat, readdir, and exists.
• The lifecycle: create, connect, suspend, and destroy, and storing the sandbox id in the Actor’s state so it reconnects after sleep.
• Streaming exec output with onData, and stopping a command with a timeout or an abort signal.
• Writing a custom provider by implementing SandboxProvider.
• How this relates to Sandboxes, which wires the same adapter into an agent’s CodingTools.