Project
Superconductor projects group together one or more repos, with an associated development environment.
To open Project Settings, go to the project and click Settings in the project navigation. From there, use the sidebar to move between the project's General, Development Environment, Agent Credentials, Network Access, Skills and MCPs, Git Integration, and Beta Features sections.
General
Use the General section to update the project's basic identity and repo connections:
- Project Name — The display name for the project throughout Superconductor.
- Repositories — The GitHub repositories connected to this project. Agents use these repos when creating branches, reading code, and opening PRs.
- Danger Zone — Administrative actions for the project, such as deleting it.
Development Environment
When you create a project, Superconductor automatically runs Assisted Environment Setup to configure the cloud dev environment where agents run. You can also tweak things manually at any time. See Development environment for details.
Agent Credentials
Configure API keys for coding agents at the project level. See Agent credentials for details on connecting credentials and precedence rules.
Network Access
Control which external domains your coding agents can access while running. See Network sandboxing for details on configuring access modes, custom rules, and trusted package registries.
Skills and MCPs
MCP servers extend agent capabilities with external tools and data sources like browsers, error trackers, analytics, and custom servers from your repos. Skills give agents access to video, audio, and image modalities built on the Agent Skills open standard.
See Skills and MCP Servers for setup details.
Git Integration
Git Sync
Control whether Superconductor automatically writes commits back to the branch after coding agent responses. When Automatically commit and push branch is enabled, Superconductor generates a commit message, creates a commit, and pushes the branch to GitHub after each coding agent message on each implementation. This happens automatically starting from the very first agent response — you don't need to create a PR first. If an agent response doesn't change any code, the commit is skipped.
This setting is off by default. To enable it, go to Project Settings and check the box under Git Sync.
When auto-commit is off (the default), you can still push changes manually using the Submit PR and Update PR buttons on any implementation.
Treatment of PRs created outside of Superconductor
When you create a PR from Superconductor, links to the implementation and live preview are automatically posted in its description. You can enable similar treatment for PRs created outside of Superconductor—useful for open-source projects or teams where some contributors prefer to work outside Superconductor.
In Project Settings, you have three options:
- Do nothing (default) – External PRs won't trigger any Superconductor activity.
- Launch a preview environment – Superconductor creates a linked ticket and spins up a live preview with an agent ready to answer questions and make changes in the branch.
- Launch a preview environment and generate a Guided Review – Superconductor creates a linked ticket, spins up a live preview, and automatically generates a Guided Review so reviewers can start from an AI-organized walkthrough of the changes.
Beta Features
Use Beta Features to manage optional project features that may not be enabled for every project. To request access to a beta feature, email help@superconductor.com.
Depending on your access and which features are available, this section can include:
- Benchmarking — Compare coding agents on real pull requests from your project. See Benchmark for details.
- Email triage — Forward customer emails to Superconductor so a PM agent can analyze them, create tickets, and draft replies. See Email triage for details.
- Meeting assistant — Invite a bot to meetings so Superconductor can capture the transcript and create tickets from action items. See Meeting assistant for details.
- QA Checks — Run an independent QA agent against your implementation to score functionality, code quality, and tests. See QA Checks for details.
- Fan-in review — Compare multiple implementations of the same ticket and get a recommendation for which one to continue with. See Fan-in review for details.