Managed Agents

Give your agents remote compute to write code, run tests, and execute commands. Connect your existing agent provider to Depot Sandboxes without managing runners or workers yourself. Keep your provider’s workflow and keep tasks running after you close your laptop.

Supported providers

Select your provider for setup instructions and connection requirements.

How Managed Agents uses Depot Sandboxes

Depot Sandboxes are standalone, isolated environments for executing commands and working with files. You can use them with your own custom agents through the Sandbox SDK, independently of Managed Agents. Depot Sandboxes currently support Linux only.

Managed Agents connects supported providers to Depot Sandboxes. Depot creates the sandbox and manages the provider’s runner or worker for you.

The agent doesn’t have to run inside the sandbox. With Claude Code, the agent loop and tools run inside the sandbox. With Claude Managed Agents, Anthropic runs the agent loop, and Depot executes commands and file operations.

Why use Depot for your agent workloads?

• Keep your existing workflow: Start sessions and interact with your agent through your provider. Depot supplies the compute for commands and tools.
• Let Depot manage the setup: Depot creates the sandbox and starts the provider's runner or worker when work arrives.
• Choose compute for your workload: Select up to 16 CPUs and 64 GB of memory for each provider connection.
• Continue work across sandboxes: Depot saves workspace snapshots and restores saved files when your session moves to a new sandbox. Continue the same conversation through your provider.
• Run work away from your laptop: Keep sessions running on Depot after you close your laptop. Commands and tools execute on Depot compute without using your laptop's CPU or memory.
• Use fast compute and networking: Run commands and tools on Depot's fast CPUs and networks.
• Reuse cached results: Supported tools use Depot Cache automatically to reuse build artifacts, test results, and other task outputs across runs.
• Access private services: Agent sandboxes automatically join your configured and enabled Tailscale tailnet to reach private services, such as databases.
• Track your team's runs: View your team's agent runs, status, timing, and failure details across providers in one Depot dashboard.

View the status of your agents on the Agent runs page in the Depot dashboard.

Session continuity

A session can continue across multiple sandbox runs. You can send another message in the same conversation through your provider, even after the previous sandbox stops.

Depot automatically saves workspace snapshots. When the session needs a new sandbox, Depot restores the latest available snapshot before starting the agent.

Snapshots preserve files, not running processes. Changes made after the last successful snapshot might not be available when the session resumes.

For your own agents or other workloads, the Sandbox SDK exposes file-based snapshots through sandbox.snapshot() and Sandbox.create(client, {snapshot}).

Depot Cache

Managed Agents automatically configures Depot Cache in agent sandboxes. Supported tools can reuse build artifacts, test results, and other task outputs across runs. They receive cache credentials and configuration without a separate setup step for each provider. Existing tool-specific cache configuration takes precedence.

Private networking

Agent sandboxes automatically join your organization's Tailscale tailnet when the integration is configured and enabled for sandboxes. Your agent's commands can access private services, such as databases, through the tailnet.

Agent sandboxes use your organization's configured Tailscale tags. Your tailnet access rules determine which private resources agents can reach.

Sandbox sizes

After connecting a provider, you can change its default sandbox size in the agent providers settings. The following sizes are available:

Each agent run uses the size configured for its connection. Compute is billed per vCPU-second, so larger sizes cost more for the same runtime.

Changing the size doesn't resize an existing sandbox. Sandbox size changes can take up to ten minutes to apply to new runs.

Pricing

Managed Agents, Depot Sandboxes, and Depot CI share one pool of included sandbox minutes. There's no separate allowance for each product. Compute is tracked and billed by the second, with no one-minute minimum per run.

Included minutes are measured at 2 vCPUs. Larger sandboxes consume the pool proportionally faster. For example, the default 4-vCPU agent sandbox uses 2 included minutes for every minute it runs.

The included minutes aren't a hard cap. Additional usage is billed automatically at $0.00005 per vCPU-second on Developer and Startup. A 4-vCPU sandbox costs $0.0002 per second after the shared allowance is used.

Depot charges for sandbox compute. Your agent provider's model usage and subscription charges are separate.

Try out Depot free for 7 days, no credit card required.

Try it free for 7 days

Plans also include separate container build and GitHub Actions runner minutes. See Pricing for plan features and costs.

Next steps

• Run Claude Code in Depot sandboxes
• Use Claude Managed Agents with Depot sandboxes
• Run Devin in Depot sandboxes
• Run OpenAI agents in Depot sandboxes