Quick start

Sign up

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

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).

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

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

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 via an integration, we still require an API key).

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.

Project setup

When you create a project, Superconductor automatically runs Assisted Environment Setup. It inspects your repo(s), configures the packages, commands, and services it needs, and gets live previews working when it can. If it needs secrets like API keys or database URLs, it will ask for them; otherwise, it auto-applies the setup for you in the background.

You can also configure things manually at any time if you prefer.

The onboarding modal walks you through the first few project steps and then brings you straight to creating your first ticket. You can click one of the sample tickets to get started fast, or write your own if you already know what you want the agents to work on.

For now, let's go ahead and submit the first ticket. “Analyze this project” is a good first one. The agent dropdown defaults to one implementation using your Default profile for integrations, if it is available for the project. Otherwise, it falls back to the best available agent for your configured credentials. You can also pick different agents if you'd like to compare. Here I am selecting an Opus 4.7 and a Codex GPT-5.5.

Ticket implementations

Clicking into a Ticket, we see the running implementations.

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

• Learn more about Implementations
• Configure your Project settings
• Invite teammates to your Workspace
• Set up Integrations for automated workflows