Integrations

Bring your own Daytona

Run agent sandboxes in your own Daytona account - what we ask for, what gets created, and how to pick which cloud new agents use.

By default, managed agents run on Agent Chatham’s own sandbox infrastructure, powered by Daytona. On any paid plan, you can instead run them in your own Daytona account - billed to you, visible in your Daytona dashboard, under your limits.

What we ask for

On the Integrations page, under Infrastructure, open the Daytona tile and click Connect. You’ll enter:

  • API key - a Daytona API key for the account agents should run in. It needs to create, start, stop and delete sandboxes.
  • Region - US or EU, where the sandboxes run.

Connect Daytona form - API key and region

The key is encrypted at rest. Connecting makes one read with it, so a key Daytona refuses fails on the form (“Daytona did not accept that API key.”) instead of at the first agent launch. Nothing is created in your account until an agent launches.

What gets created in your account

  • One sandbox per agent, in the region you picked, built from the public Agent Chatham image.
  • Every sandbox carries agent_chatham_* labels naming the workspace and the organization it belongs to. We only ever list, clean up or delete sandboxes that carry our workspace label - anything else in your account is left alone.

Azure and Daytona together

An Enterprise organization can connect both Daytona and Azure. New agents then run on the default account. With both connected, a New agents run on switch appears under the Infrastructure heading - for example Azure · rg-agents | Daytona · us - and clicking the other half makes that account the default.

Until you choose, the default is the account you connected first. The choice applies to new agents only - agents already running stay where they are. Disconnecting the default hands it to the other account.

Disconnecting

Disconnect refuses to run while agents are still placed on the account (“This account still has agents on it. Terminate them before disconnecting.”). Once they’re gone, it deletes any sandboxes we left behind, takes the account out of service, and forgets the API key. If your plan changes, an already-connected account keeps working and can always be disconnected.