Primary worktree ★

The starred branch row in the sidebar is the project’s primary working copy. It represents the original checkout that Superconductor opened or cloned.

A star marks the primary working copy so you can find it next to task worktrees. Superconductor does not create it through git worktree add; it is the repository’s main checkout.

When to use it

Use the primary worktree for a direct view of the project checkout:

• Ask questions about the codebase.
• Run a quick terminal or chat session.
• Inspect files without creating a task worktree.
• Make a small change or pull request that needs no separate working directory.

For larger work, parallel agent sessions, risky edits, or changes you want isolated from the project checkout, create a task worktree.

Hide the primary worktree

If you work mainly from task worktrees, hide the primary worktree from the project list.

Open the primary worktree’s context menu and choose Hide primary worktree. To show it again, open the project menu and choose Show primary worktree.

Hiding it changes only sidebar visibility. The project checkout, files, and branch remain unchanged. The visibility setting saves with the project and persists across restarts.

Switching branches

Branch switching runs on the primary working copy. Use it to check out an existing branch or move between branches without creating a task worktree.

If a branch already has its own task worktree, open that worktree rather than switching the primary working copy to the same branch.

Primary worktree and task worktrees

Task worktrees are separate working directories for branch-backed tasks. They give you isolation, parallel agents, and a clean removal path after a task merges or you discard it.

The primary working copy stays with the project. It is the stable place to understand the repository, start small work, and switch between branches when a task worktree would be excessive.