Supported forges

Superconductor works with any local git repository for workspaces, terminals, chat, and diff review. Some features also depend on the forge behind your git remote. When a supported forge hosts a repository, Superconductor shows pull request or merge request metadata, checks, review state, and branch actions.

Set up forge access before you rely on these remote-aware workflows. Superconductor runs the provider CLI locally and uses the credentials you have already configured.

Forge support

Superconductor includes built-in forge support for:

• GitHub.
• GitHub Enterprise hosts.
• GitLab.
• Self-managed GitLab hosts when the remote hostname looks like GitLab, resolves through SSH config, or is known to the GitLab CLI.

The forge integration model uses provider adapters and stays provider-agnostic, but each provider implements its own adapter. Today, those adapters cover GitHub and GitLab. If another forge exposes the needed repository, pull request, branch, and check data through a local CLI, file a feature request in Discord.

Repositories without a supported remote still work for local workspaces, terminals, chat, and diffs, but lack forge-aware PR or MR metadata.

Getting started requirements

For GitHub workflows, install and authenticate the GitHub CLI:

gh auth status

For GitLab workflows, install and authenticate the GitLab CLI:

glab auth status

Superconductor runs forge commands locally and stores no separate GitHub or GitLab credentials.

Remote detection

Superconductor inspects git remotes, preferring origin, to detect the provider and repository identity.

Supported remote styles include common HTTPS and SSH forms. For GitHub Enterprise and GitLab self-managed hosts, Superconductor preserves the host from the remote URL and passes it to the provider CLI when needed.

If forge features do not appear:

1. Run git remote -v.
2. Confirm the repository has a supported GitHub or GitLab remote. Superconductor prefers origin, but detects other named remotes.
3. Confirm the remote URL uses a supported HTTPS or SSH form.
4. Confirm gh or glab is installed and authenticated.
5. Confirm your CLI has access to that host and repository.

Pull request and merge request state

When a PR or MR is associated with a worktree branch, Superconductor shows:

• Review request metadata.
• Target branch.
• Checks or pipeline status.
• Mergeability and conflict state.
• Draft, open, merged, or closed state.
• GitHub unresolved review-thread counts, and GitLab blocked or discussion-related merge status when available.

The active worktree polls the provider directly. Inactive worktrees rely on cached or batch-refreshed PR/MR context to reduce background traffic.

Target branch and forge branch

Superconductor tracks its own target branch separately from the forge target branch. When the two diverge, local review summaries and remote PR metadata describe different merge targets.

Check the local target branch with:

sc worktree status --json

Then compare it to the PR or MR target branch in the forge.

Unsupported providers

For remotes other than GitHub or GitLab, Superconductor still supports local git workflows. Use standard git commands or your provider’s CLI for PR actions, and use Superconductor for isolated workspaces, terminals, sessions, and local review.