mirror of
https://github.com/harivansh-afk/sandbox-agent.git
synced 2026-04-15 22:03:48 +00:00
6a42f06342
- Add built-in sandbox providers (local, docker, e2b, daytona, vercel, cloudflare) to the TypeScript SDK so users import directly instead of passing client instances - Restructure docs: rename architecture to orchestration-architecture, add new architecture page for server overview, improve getting started flow - Rewrite quickstart to be TypeScript-first with provider CodeGroup and custom provider accordion - Update all examples to use new provider APIs - Update persist drivers and foundry for new SDK surface Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
43 lines
1.5 KiB
Text
43 lines
1.5 KiB
Text
---
|
|
title: "Orchestration Architecture"
|
|
description: "Production topology, backend requirements, and session persistence."
|
|
icon: "sitemap"
|
|
---
|
|
|
|
This page covers production topology and backend requirements. Read [Architecture](/architecture) first for an overview of how the server, SDK, and agent processes fit together.
|
|
|
|
## Suggested Topology
|
|
|
|
Run the SDK on your backend, then call it from your frontend.
|
|
|
|
This extra hop is recommended because it keeps auth/token logic on the backend and makes persistence simpler.
|
|
|
|
```mermaid placement="top-right"
|
|
flowchart LR
|
|
BROWSER["Browser"]
|
|
subgraph BACKEND["Your backend"]
|
|
direction TB
|
|
SDK["Sandbox Agent SDK"]
|
|
end
|
|
subgraph SANDBOX_SIMPLE["Sandbox"]
|
|
SERVER_SIMPLE["Sandbox Agent server"]
|
|
end
|
|
|
|
BROWSER --> BACKEND
|
|
BACKEND --> SDK --> SERVER_SIMPLE
|
|
```
|
|
|
|
### Backend requirements
|
|
|
|
Your backend layer needs to handle:
|
|
|
|
- **Long-running connections**: prompts can take minutes.
|
|
- **Session affinity**: follow-up messages must reach the same session.
|
|
- **State between requests**: session metadata and event history must persist across requests.
|
|
- **Graceful recovery**: sessions should resume after backend restarts.
|
|
|
|
We recommend [Rivet](https://rivet.dev) over serverless because actors natively support the long-lived connections, session routing, and state persistence that agent workloads require.
|
|
|
|
## Session persistence
|
|
|
|
For storage driver options and replay behavior, see [Persisting Sessions](/session-persistence).
|