# Your Daytona sandboxes. Run from your agent.

Source: https://corespeed.io/integrations/daytona

Connect Daytona to Claude Code, Codex, Cursor or any MCP agent through CoreSpeed. Your agent creates and starts Daytona sandboxes, runs shell commands in them, reads and writes their files, and manages snapshots. It uses a Daytona API key you create, whose permissions decide which write tools work, and Daytona bills a sandbox while it runs.

## Set up an agent

Give your agent this line: `set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl)`

It fetches the skill at https://corespeed.io/SKILL.md, adds the CoreSpeed MCP server, signs you in (or up), and keeps the skill for next time. Connect Daytona after setup. Access follows the connected account and its permissions. Create an account: https://app.corespeed.io/sign-up

## Run it in a sandbox. Read the result in your agent

Your agent finds the sandbox, runs the command, and reads the files it needs to explain the output.

You ask your agent: "Run the test suite in the api-tests sandbox and tell me which tests fail and why. Do not change any files."

It calls CoreSpeed:

- `daytona__get_sandbox`: ok, 284 ms
- `daytona__execute_command`: ok, 41230 ms
- `daytona__read_file`: ok, 233 ms

It reads from: Daytona.

### Test run: Two tests fail, one cause.

Both failures are in the billing tests. They expect a 30-day trial; the code now gives 14 days.

**Failing**

- test_trial_length
- test_trial_end_email

**Next**

- Decide whether the tests or the trial length is wrong.

_Illustrative sandbox · Fictional data · No file changed_

All connectors: https://corespeed.io/docs/connectors

## From a sandbox to a result you can read

Requests you can make once Daytona is connected. The data is fictional.

### Look inside a sandbox

api-tests · /workspace · Files in the sandbox

- Sandbox: api-tests
- Latest: test-report.xml
- Nothing changed

### Run a command

Run the tests · Exit code and output

- Command: pytest -q
- Result: 148 passed
- Exit 0

### Hold a delete for a person

Delete a sandbox · This cannot be undone

- Sandbox: old-demo
- Policy: Ask before deleting a sandbox
- Waiting for you

## Keep your agent. Bring your work

One CoreSpeed account, across compatible agents.

1. **Set up CoreSpeed**: Give your agent the setup line. It adds CoreSpeed and signs you in.
2. **Connect Daytona**: Authorize the account and the content you need.
3. **Start with one task**: Ask for a summary, a brief, or a draft. Review the answer.

Setup guides: Claude Code https://corespeed.io/docs/mcp#claude-code · Codex https://corespeed.io/docs/mcp#codex · Cursor https://corespeed.io/docs/mcp#cursor

## Questions

### Does a sandbox cost money while it runs?

Yes. Daytona bills its usage for as long as a sandbox runs. Ask your agent to stop or archive it when the work is done.

### What decides which tools work?

The permissions on your Daytona API key. Reads are always included; creating, deleting and snapshot tools need the matching write permissions.

### Can my agent delete a sandbox on its own?

Deleting is a separate tool call, and it cannot be undone. Approvals can hold it for a person first. How approvals work: https://corespeed.io/docs/approvals

### Do I have to switch agents?

No. CoreSpeed adds tools to the agent you already use: Claude Code, Codex, Cursor, or another MCP client. Each one signs in once.

### Can my agent access every account in our organization?

No. Access follows your CoreSpeed identity, each connection's visibility, and the app's own permissions. Personal connections stay private.

### Does this work without connecting an account?

No. Connect the app's account first; your CoreSpeed workspace shows what each app needs. The examples on this page use fictional data. All connectors: https://corespeed.io/docs/connectors

Every tool and price: https://corespeed.io/catalog/daytona

## Related pages

- [AWS for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/aws): Let your agent call any AWS API with your IAM credentials. Writes and secret reads can wait for a person.
- [MCP gateway for your agents and tools](https://corespeed.io/solutions/mcp-gateway): Reach connected apps, built-in tools, and your own remote MCP servers through one authenticated CoreSpeed MCP endpoint.

## Sources

- Connectors: https://corespeed.io/docs/connectors
- Daytona documentation: https://www.daytona.io/docs/
- Daytona sandboxes: https://www.daytona.io/docs/en/sandboxes
- Daytona API keys: https://www.daytona.io/docs/en/api-keys

Reviewed 2026-11-10.

## Links

- Product overview: https://corespeed.io/ (Markdown: https://corespeed.io/index.md)
- All integrations: https://corespeed.io/integrations (Markdown: https://corespeed.io/integrations.md)
- Documentation: https://corespeed.io/docs
- Pricing: https://corespeed.io/pricing (Markdown: https://corespeed.io/pricing.md)