Use remote sandboxes

Run Deep Agents Code tool execution in LangSmith, Daytona, Modal, Runloop, or AgentCore sandboxes. Install provider extras, set credentials, and use flags and setup scripts.

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.

1. Install provider dependency

   LangSmith

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

   Daytona

   uv tool install 'deepagents-code[daytona]'
   

   Modal

   uv tool install 'deepagents-code[modal]'
   

   Runloop

   uv tool install 'deepagents-code[runloop]'
   

   AgentCore

   uv tool install 'deepagents-code[agentcore]'
   

   To install support for every sandbox provider at once, use the all-sandboxes extra: uv tool install 'deepagents-code[all-sandboxes]'.

2. Set provider credentials

   LangSmith

   export LANGSMITH_API_KEY="your-key"
   

   Daytona

   export DAYTONA_API_KEY="your-key"
   

   Modal

   modal setup
   

   Runloop

   export RUNLOOP_API_KEY="your-key"
   

   AgentCore

   export AWS_ACCESS_KEY_ID="your-key"
   export AWS_SECRET_ACCESS_KEY="your-secret"
   export AWS_REGION="us-west-2"
   
   # Only when using temporary/STS credentials:
   export AWS_SESSION_TOKEN="session-token"
   
3. Run Deep Agents Code with a sandbox

   LangSmith

   dcode --sandbox langsmith
   

   Daytona

   dcode --sandbox daytona
   

   Modal

   dcode --sandbox modal
   

   Runloop

   dcode --sandbox runloop
   

   AgentCore

   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-snapshot-name NAME	Use or create a sandbox snapshot (LangSmith only). Cannot be combined with --sandbox-id
--sandbox-setup PATH	Path to a setup script to run inside the sandbox upon creation

Each provider exposes a default working directory inside the sandbox. Setup scripts and execute commands run from this directory unless overridden:

Provider	Working directory
LangSmith	/root
Daytona	/home/daytona
Modal	/workspace
Runloop	/home/user
AgentCore	/tmp

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.