Skip to main content
Daytona provides provider-managed remote sandboxes. Use it when you want a remote workspace per task without consuming local compute, especially for SWE-bench and Terminal-Bench smoke tests.

First-Time Setup

  1. Create a Daytona account from the official dashboard.
  2. Open the API keys page and create a key with sandbox permissions.
  3. Export the key in the shell that runs AgentCompass.
  4. Run a single task before increasing concurrency.
DAYTONA_API_KEY is the only value most users need. DAYTONA_API_URL and DAYTONA_TARGET are optional and should be set only when your Daytona workspace requires a non-default API endpoint or target. AgentCompass authentication precedence is:
Do not commit Daytona API keys to config/defaults.yaml. Use environment variables or a private config file passed with --config.

Verify Credentials

The most useful verification is an AgentCompass smoke test because it checks credentials, sandbox startup, recipe image selection, file operations, and harness execution together.

Single Terminal-Bench Instance

This is the recommended provider smoke test because it runs one task and lets the recipe infer the task image.

Provider Params

Common Daytona overrides live under environments.daytona or --env-params:

SWE-bench Verified

Recipes set compatible images and workspaces for supported benchmark/provider pairs. Pass --env-params only for deliberate overrides.