GitHub

Enabling the GitHub integration

GitHub is connected at two levels:

1. Workspace — Install the Superconductor GitHub App on your GitHub organization or account during workspace setup. This gives your workspace access to repositories. If you create additional workspaces, you'll be prompted to connect GitHub for each one. You can manage installations and set repository defaults in Workspace Settings → Integrations.
2. Project — Link specific repositories to a project when creating or editing the project. Projects can only use repos that are already connected at the workspace level.

Creating pull requests from Superconductor

You can create and manage pull requests directly from the Superconductor app. See Creating pull requests in the Implementation docs for details.

Tagging Superconductor in GitHub

Tag @superconductor or use /sc in PR comments (including inline review comments) to interact with agents:

• Existing implementation: If the PR has an associated Superconductor implementation, the agent will work in that context and respond to your comment.
• New implementation: If not, a new ticket and implementation will be created in the Superconductor project linked to this repo that best matches your workspaces.

This lets you request changes, ask questions, or get help directly from GitHub without switching to the Superconductor app.

PRs created outside of Superconductor

Configure how Superconductor handles PRs created outside the app in Project Settings. When enabled, any new PR opened on the project's repositories will automatically create a linked Superconductor ticket with a live preview and an agent ready to help. See Treatment of PRs created outside of Superconductor for details.

Matching repos to projects

You can set default projects for repositories in Workspace Settings → Integrations → GitHub. This determines which project is used when @superconductor mentions on PRs in that repository create new tickets. If no default is set, Superconductor will try to find a matching project automatically. If it can't determine which project to use, it will reply on the PR asking you to specify one.

Tips for using the GitHub integration

Choose a specific model

When you don't specify a model, Superconductor automatically picks the best available default based on your project's configured credentials. The fallback order is:

1. Codex GPT-5.3 (requires a connected ChatGPT Pro or Plus plan)
2. Claude Code Opus 4.6 (requires an Anthropic API key or connected Claude plan)
3. Codex GPT-5.2 (requires an OpenAI API key or connected ChatGPT plan)

Superconductor selects the first model in this list for which your project has valid credentials configured.

To pick a specific model instead, add model:MODEL_NAME to your comment:

@superconductor model:claude_opus Fix the failing test in auth_controller

You can also use quotes for model names with spaces: model:"gpt-5.2 medium". Models are matched fuzzily, so model:opus will match claude_opus.

Specify a project

If a repo belongs to multiple projects, tell Superconductor which one to use with project:PROJECT_NAME:

@superconductor project:"My Project" Add dark mode support

If the repo only belongs to one project, you can skip this — Superconductor picks it automatically.

Use inline review comments for file-specific requests

When you mention @superconductor in an inline review comment on a specific file or line, the agent automatically gets the file path, line numbers, and diff context. This is a great way to point the agent at exactly the code you want changed.

View directory of projects and models

Type @superconductor help to see a list of available projects and models you can use.

Support for Issues, Projects, and Wikis

We currently do not support GitHub Issues, Projects, or Wikis as ticket sources. Please let us know if you'd like us to!