Which agents run on which key
Claude Code needs your own key to run in the cloud. Its terms do not let a
product pay for Claude Code usage on its users’ behalf: each user’s usage has
to be billed to them by Anthropic. The Orchestra agent is built on the Claude
Agent SDK, which may run on Orchestra’s key, so you can use it without a key
of your own.
Cloud sessions in every workspace have a monthly compute budget and a limit on
how many run at once. Those cover the machines Orchestra runs, so they apply
the same whichever key a session uses.
Add a key
- Create an API key in the Claude Console.
- Open Settings, then Integrations.
- Under Models, paste the key and click Save key.
Remove a key
Click Remove next to the key. It takes effect within a minute: a Claude Code session that is already running stops at its next model request, and other sessions carry on, on Orchestra’s key. To stop the key working anywhere at once, also revoke it in the Claude Console.Where the key goes
- The key is stored encrypted, per workspace, and only Orchestra’s servers can read it. No other workspace can read, use or remove it.
- It never enters a session’s machine. The agent sends its model requests to Orchestra, which adds the key on the way to Anthropic.
- It is never written to Orchestra’s history, logs or error messages. Adding and removing it are recorded, with who did it and when, but not the key.