Superconductor Docs

Quick start

Get started with Superconductor in minutes.

Sign up

We support signing up with Google, Apple, GitHub, or email/password.

Sign up form with OAuth options for Google, GitHub, and Apple

Workspace setup

Upon signup, you will set up your personal Workspace. (If you were invited by a teammate to a shared Workspace, then you’ll see their Project list immediately, but can still set up your own Workspace if you want).

Workspace setup wizard showing three steps: Connect GitHub, Add API Keys, and Create Project

Because Projects must have a linked GitHub repository or repositories, the first step is to connect to GitHub.

GitHub OAuth authorization prompt requesting permissions for Superconductor

You can select all or any subset of repos that you want Superconductor to access.

GitHub repository selection with all or selected repositories permission options

The next step is to set up API keys. We also support connecting your personal Claude Pro/Max and OpenAI accounts for Claude Code and Codex, which will be used for implementations that you launch directly. (For implementations that are launched automatically, we still require an API key).

API keys configuration step with Claude Code, Codex, Gemini, Amp, and Opencode options

Lastly, you will create your first project. A project must have at least one repo, but can have any number of them. Coding agents launched on a ticket in a project will be able to navigate into all of the linked repos as need be. See the GitHub integration docs for more on connecting and managing repositories.

Create first project with repository selection from connected GitHub repos

Project setup

When a Project is created, its development environment is built automatically. The default Environment has Node, Python, 2 vCPUs, 4 GB memory, and 10 GB disk space.

Project dashboard showing development environment built successfully with ticket creation

We will take a deeper look at setting up the project environment later, but for now let's go ahead and submit the first ticket. “Analyze this project” is a good first one, and here I am selecting an Opus 4.6 and a Codex GPT 5.3.

Create ticket with agent model selection dropdown showing Claude Code Opus 4.6 and Codex GPT-5.3 options

Ticket implementations

Clicking into a Ticket, we see the running implementations.

Ticket view showing running implementations from Claude Code Opus 4.6 and Codex GPT-5.3

When one finishes, we can check it out. Click into an implementation to:

  • Review the diff: See all code changes with our Guided Review feature
  • Chat with the agent: Continue the conversation to refine the implementation
  • Live preview: Test the changes in a live environment with terminal access

Next steps

On this page