Manage API keys
This guide shows you where each credential Control Center uses is stored and how to change it.
Nothing is stored on the machine you are typing on. Every credential lives on the server; which one answers a given request depends on whether there is a human behind it.
| Credential | Stored | Who uses it |
|---|---|---|
| Your forge / ticketing sign-in | The server’s 0600 secrets file, keyed by your user id | Anything you do: the PR surface, reviews, merges, your Linear actions |
| The server’s provider apps | The same file, plus server_settings for the non-secrets |
Signing people in, and one-repository tokens for agents, pipelines and polling |
| The Connect install key | The same file (connect_install_key) |
Identifying this server to Control Center Connect |
| Model provider keys and OAuth tokens | The server’s own credential store | The built-in adapter, for every workspace on the install |
| Slack bot credentials | <dataDir>/<workspaceId>/chat_credentials/ on the server |
The chat bridge for that workspace: your own app’s tokens, or the shared app’s sealed grant |
| External CLI credentials | Whatever that CLI uses | Claude Code, on the server host |
GitHub: your sign-in, and one-repository tokens
Section titled “GitHub: your sign-in, and one-repository tokens”- Yours, from Sign in to GitHub. It is what every request made on your behalf uses, so a review posted for you carries your name. Another member cannot use it, and they sign in themselves. There is no GitHub token to paste
- Work with no one typing (agents, pipelines, polling, bot replies) gets a token for one repository at a time, minted from the server’s GitHub App or through Control Center Connect, and limited to what an accountable member can do there. It is never your sign-in handed over whole
Yours is set in the Code hosting card at Settings → You → Profile; the server’s app in Provider apps at Settings → Server → Single sign-on. See Set up GitHub integration and Create the GitHub App.
GitLab and Bitbucket still take a pasted personal token, stored the same way. See Connect a code host.
Set model provider keys
Section titled “Set model provider keys”The built-in adapter authenticates providers itself and those credentials live on the server.
- Go to Settings → Server → Model providers
- Scroll to Providers & models
- Connect the provider — browser OAuth for OpenAI, Codex, Cursor and Kimi Code; an API key for Anthropic and the rest
See Manage adapters and models for the full list and for adding a custom endpoint.
These credentials are host-global: one key serves every workspace on the install. OAuth tokens are refreshed before they expire.
Claude Code signs in through Claude Code accounts under Settings → Server →
Model providers: each account gets its own configuration directory on the
server, and you run the claude auth login command the app shows you there.
The per-adapter Environment variables dialog looks like a place to put a key for one of them, but it is not: it writes to your device, while the server reads its own copy and nothing bridges the two. See Manage adapters and models.
Connect a ticketing vendor
Section titled “Connect a ticketing vendor”The Ticketing card on Settings → Workspace → Integrations holds the workspace’s side: which vendor your tickets live in, and who Control Center is when it works there on its own. Choosing Local hides the Linear rows — local tickets live in this server’s own database and have nothing to authenticate to.
Linear has two sign-ins and no pasted key: Linear is yours, for what you do, and lives on Settings → You → Profile; Linear automation is the workspace’s Control Center app, connected by an admin on the Ticketing card, for ticket sync, pipelines and agents. The server may also hold a Service API key (Provider apps) for workspaces without automation connected. No ticketing credential is injected into an agent’s sandbox; agents write tickets through Control Center’s tools, which ask the Write to an external tracker rule. See Set up Linear integration.
Rotate or revoke
Section titled “Rotate or revoke”- Your GitHub sign-in: press Disconnect, then Sign in to GitHub again. Disconnecting also drops every token the server minted on your behalf
- A GitLab or Bitbucket token: press Update token and paste the new one, then revoke the old one on the forge
- The server’s app: generate a new private key or client secret on the app’s provider page, paste it in Provider apps and press Test
- The Connect install key: the server owner presses Rotate key on the Control Center Connect card. Everybody who signed in through Connect signs in again. If a Connect server can’t be reached, nothing changes and you are offered Rotate anyway. See Rotate the install key
- A model provider: on its row, sign out (OAuth) or remove the key, then connect again
- Slack: for your own app, re-paste the tokens in the connect dialog. The shared Control Center app has no token to rotate: its bot token is renewed through Connect, and Disconnect revokes it and uninstalls the bot from Slack. See Set up Slack integration
Troubleshooting
Section titled “Troubleshooting”A GitLab or Bitbucket token works in curl but not here
Section titled “A GitLab or Bitbucket token works in curl but not here”Check the Code hosting row. If it reads “Not connected” or asks you to connect again, your token was not saved or was rejected. For Bitbucket, enter your Atlassian account email together with the API token.
A GitLab or Bitbucket token is accepted but later requests fail
Section titled “A GitLab or Bitbucket token is accepted but later requests fail”The token is probed as it is stored, so the row names the account behind it — but only the account, not the scopes. A token with too few scopes connects and then fails individual requests. Check its scopes and expiry on the forge.
A provider says sign-in isn’t set up on this server
Section titled “A provider says sign-in isn’t set up on this server”The server has neither its own app for that provider nor Control Center Connect. The server owner picks one in Settings → Server → Single sign-on.