Use remote sandboxes

Deep Agents Code uses the sandbox as tool pattern: the dcode process (LLM loop, memory, tool dispatch) runs on your machine, but agent tool calls (read_file, write_file, execute, etc.) target the remote sandbox, not your local filesystem. To get files into the sandbox, use a setup script or the provider’s file transfer APIs (see Working with files). For a deeper look at sandbox architecture, integration patterns, and security best practices, see Sandboxes.

Install provider dependency

LangSmith
Daytona
Modal
Runloop
AgentCore

Included by default when installing deepagents-code. No extra installation needed.

uv tool install deepagents-code --with langchain-daytona

uv tool install deepagents-code --with langchain-runloop

uv tool install deepagents-code --with langchain-agentcore-codeinterpreter

Set provider credentials

LangSmith
Daytona
Modal
Runloop
AgentCore

export LANGSMITH_API_KEY="your-key"

export DAYTONA_API_KEY="your-key"

export RUNLOOP_API_KEY="your-key"

export AWS_ACCESS_KEY_ID="your-key"
export AWS_SECRET_ACCESS_KEY="your-secret"
export AWS_SESSION_TOKEN="session-token"
export AWS_REGION="us-west-2"

Run Deep Agents Code with a sandbox

LangSmith
Daytona
Modal
Runloop
AgentCore

dcode --sandbox langsmith

dcode --sandbox daytona

dcode --sandbox runloop

dcode --sandbox agentcore

Sandbox flags and examples

Flag	Description
`--sandbox TYPE`	Sandbox provider to use: `langsmith`, `agentcore`, `modal`, `daytona`, or `runloop` (default: `none`)
`--sandbox-id ID`	Reuse an existing sandbox by ID instead of creating a new one. Skips creation and cleanup. Refer to your sandbox documentation for more
`--sandbox-setup PATH`	Path to a setup script to run inside the sandbox upon creation

Examples:

# Create a new Daytona sandbox
dcode --sandbox daytona

# Reuse an existing sandbox (skips creation and cleanup)
dcode --sandbox runloop --sandbox-id dbx_abc123

# Run a setup script after sandbox creation
dcode --sandbox modal --sandbox-setup ./setup.sh

Setup scripts

Use --sandbox-setup to run a shell script inside the sandbox after creation. This is useful for cloning repos, installing dependencies, and configuring environment variables.

setup.sh

#!/bin/bash
set -e

# Clone repository using GitHub token
git clone https://x-access-token:${GITHUB_TOKEN}@github.com/username/repo.git $HOME/workspace
cd $HOME/workspace

# Make environment variables persistent
cat >> ~/.bashrc <<'EOF'
export GITHUB_TOKEN="${GITHUB_TOKEN}"
export OPENAI_API_KEY="${OPENAI_API_KEY}"
cd $HOME/workspace
EOF
source ~/.bashrc

Deep Agents Code expands ${VAR} references in setup scripts using your local environment variables. Store secrets in a local .env file for the setup script to access.

Sandboxes isolate code execution, but agents remain vulnerable to prompt injection with untrusted inputs. Use human-in-the-loop approval, short-lived secrets, and trusted setup scripts only. See Security considerations for details.

Connect these docs to Claude, VSCode, and more via MCP for real-time answers.

Edit this page on GitHub or file an issue.

Get started

Deployment

Core capabilities

Frontend

Protocols

Code

Sandbox flags and examples

Setup scripts

​Sandbox flags and examples

​Setup scripts

Sandbox flags and examples

Setup scripts