Troubleshooting

Source: docs/troubleshooting.mdx Canonical URL: https://sandboxagent.dev/docs/troubleshooting Description: Common issues and solutions when running sandbox-agent

"Agent Process Exited" immediately after sending a message

This typically means the agent (Claude, Codex) crashed on startup. Common causes:

1. Network restrictions

The sandbox cannot reach the AI provider's API (api.anthropic.com or api.openai.com). Test connectivity with:

curl -s -o /dev/null -w '%{http_code}' --connect-timeout 5 https://api.anthropic.com/v1/messages

A 000 or timeout means the network is blocked. See Daytona Network Restrictions below.

2. Missing API key

Ensure ANTHROPIC_API_KEY or OPENAI_API_KEY is set in the sandbox environment, not just locally.

3. Agent binary not found

Verify the agent is installed:

ls -la ~/.local/share/sandbox-agent/bin/

Daytona Network Restrictions

Daytona sandboxes have tier-based network access:

Tier	Network Access
Tier 1 & 2	Restricted. Cannot be overridden. AI provider APIs blocked by default.
Tier 3 & 4	Full internet access. Custom allowlists supported.

If you're on Tier 1/2 and agents fail immediately, you have two options:

Upgrade to Tier 3+ for full network access
Contact Daytona support to whitelist api.anthropic.com and api.openai.com for your organization

The networkAllowList parameter only works on Tier 3+:

await daytona.create({
  snapshot: "my-snapshot",
  envVars: { ANTHROPIC_API_KEY: "..." },
  networkAllowList: "api.anthropic.com,api.openai.com", // Tier 3+ only
});

See Daytona Network Limits documentation for details.

1.8 KiB Raw Permalink Blame History