Credentials
Save provider access once in Settings → Credentials so you can select it for projects and runs. The providers and OAuth paths available to you depend on the deployment.
Add or remove credentials
The page supports these saved credential types:
| Credential | Purpose |
|---|---|
| Anthropic API key or Claude OAuth | Anthropic model access. |
| OpenAI API key or ChatGPT OAuth | OpenAI model access. |
| OpenRouter API key | OpenRouter model access. |
| xAI / Grok API key | xAI model access. |
| GitHub Copilot OAuth | Copilot model access. |
| GitHub token | GitHub access for work that needs it. |
Enter or replace values, then select Save credentials. Saved values are write-only: the page shows that a credential is saved, but not its value. Select Remove beside a saved item to remove it.
The desktop app can offer Use your local sign-in when it detects supported local provider credentials. This option is not available in every environment.
OAuth
Use the relevant OAuth card when it is available. The page can also accept manually supplied OAuth JSON for Claude, ChatGPT/OpenAI, or Copilot. Follow your workspace’s provider-access policy before adding credentials.
Integration credentials
Integration credentials are named groups of secret key/value pairs. They are available for MCP server configuration under Resources.
- In Integration credentials, enter an integration name.
- Add its secret key/value rows.
- Save the integration.
The app lists saved integration and key names, not secret values. Use plain environment values only for non-secret configuration.
Share credentials deliberately
The Share action can copy selected saved credentials to another workspace user. The recipient can use the copied credentials in their own runs, and usage counts against the same provider account. Copies do not stay synchronized.
Only share credentials when your organization allows it. A project or run share alone does not copy your credentials.
Use credentials safely
- Do not paste credentials into chat.
- Use saved credentials rather than putting secrets in project instructions.
- Remove or rotate credentials according to your organization policy.
- Treat a GitHub token for desktop updates as separate from the GitHub token on this page.