Workspaces, projects, and worktrees
A workspace is a top-level context. It holds one or more projects and carries its own chrome and accent colors, agent defaults, and workflow settings.
Superconductor opens Git repositories and plain project folders inside a workspace. For Git repositories, it uses git worktrees to isolate task branches; each worktree gets a working directory that shares the repository’s history.
Plain folders open as non-Git projects for local files, terminals, and agent sessions. They do not support branch-backed worktrees, target-branch comparisons, or Git review until you initialize Git.
Git worktrees
Section titled “Git worktrees”Git worktrees let one repository check out multiple working directories at once. Superconductor uses that feature for task branches.
For a plain folder, Superconductor keeps you in that folder rather than creating a worktree. Initialize Git first when you need isolated task directories.
Workspace context
Section titled “Workspace context”Workspaces hold durable context such as personal work, company work, a client, or a group of related repositories. Workspace-level settings include:
- Chrome and accent colors for the active context.
- Agent provider and model defaults.
- Per-workspace provider profile overrides.
- Multiple projects grouped under one workspace.
For theme and layout controls, see Layout, sidebars, and PiP.
Branches
Section titled “Branches”You name a branch when you create or rename a worktree. Example branch names:
feat/docs-systemfix/api-download-redirectrefactor/sidebar-stateTarget branch
Section titled “Target branch”The target branch is the branch Superconductor compares against for status and review. It defaults to the remote default branch (origin/HEAD), falling back to origin/main, origin/master, or the local main or master. Release branches work, too.
Set the target branch to the branch into which the work will merge.
Task directories
Section titled “Task directories”Each Git-backed task worktree owns a directory. Terminals and agent sessions opened from that worktree run there.
Cleanup
Section titled “Cleanup”After a branch merges or you no longer need it, remove the task worktree from Superconductor. Decide whether to commit, push, or discard changes before you delete the worktree.