Superconductor Docs

Agent credentials

Configure API keys and connected plans for coding agents.

Agent credentials configuration showing Claude Code, Amp, Gemini, Codex, and Opencode with API key fields

Superconductor works on a BYOK (bring-your-own-keys) basis, meaning that requests to the coding agent models are made using your own keys or credentials.

Connecting credentials

Agent API keys can be defined on the Workspace, or on the Project.

For Claude Code and Codex agents, we additionally support individual users connecting their Claude and ChatGPT premium plans instead of using API keys. This can be done either in Workspace settings, Project settings, or Account settings.

Deciding which credentials to use

If the agent is launched automatically (e.g. by an external PR, Slack, or Email triage), we use API keys only, following precedence: Project key first, then Workspace key.

If the agent is launched manually by a user, we follow this precedence order:

  1. That user's connected plan (if any)
  2. Project API key (if any)
  3. Workspace API key

What if my connected plan hits its usage limit? Superconductor does not automatically fall back to an API key. The implementation will stop, and you'll see a message in the chat indicating that your plan's limit has been reached and when it resets. For Claude, you can disconnect your plan in your account settings and use an API key instead until the limit resets.

Benchmarking

Agent API keys are also required to include agents in Benchmark runs. Only agents with configured keys will be available for selection when setting up a benchmark. You don't need to provide keys for the evaluation models — Superconductor handles that.

On this page