Introduction
Superconductor is a native macOS workspace for agentic engineering. It organizes projects into durable workspaces, isolates Git-backed tasks in their own worktrees, ties terminals and chat sessions to the code they change, and offers a built-in surface for reviewing diffs before you merge.
Bring your own provider CLIs and subscriptions. Superconductor routes no provider traffic through its own servers and stores no account. It organizes the workspace, session, and review flow around the tools you already use.
Why Superconductor
Section titled “Why Superconductor”- 100% Rust, GPU-rendered. Native macOS binary on Metal. No Electron, no embedded browser. Cold start in under 50ms.
- Any agent, any model. Claude, Codex, Cursor, Gemini, Grok, OpenCode, Pi, Kiro, and Copilot in terminal or native chat. Pick the provider, model, and reasoning effort per session.
- Multi-account profiles. Run work and personal Claude side by side. Profiles cascade global → workspace → project, so each repository launches with the right config.
- Parallel by default. Each task runs in its own git worktree. Concurrent agents never share a working copy or step on each other’s changes.
- Local-first and private. No account. Anonymous-only telemetry. Prompts, code, and paths stay on your Mac. Use your own subscriptions; nothing is proxied.
- Pick up where you left off. Close the app, reopen it. Every agent session, split layout, and PiP window restores intact.
- Scriptable. The
scCLI and local API drive worktrees, tabs, and chat from agents or scripts. Repository-scoped setup, run, and cleanup hooks live in your repo. - Cross-repo workspaces. Group frontend, backend, and shared SDK under one parent. Coordinate review across repositories in one place.
Start here
Section titled “Start here”- Install Superconductor.
- Add your first project in Your first workspace.
- Run your first agent in Run agents.
- Inspect the result in Review changes.
- Ship through Pull requests and review.
Mental model
Section titled “Mental model”Superconductor organizes work around workspaces and git worktrees:
- A workspace is the durable context that holds one or many projects.
- Git-backed projects create worktrees for task branches.
- The parent repository remains your source of truth.
- Agents work inside the selected project or task worktree.
- You inspect the resulting changes before they land.
This structure separates workspace context from task-specific branch directories.
Get help
Section titled “Get help”Join the Discord community for setup questions, provider issues, and product feedback.