Every pane is an isolated workspace.

Creating a pane

Create Pane

Base branch

Feature name

Creates a new git worktree with an isolated branch

Creating a pane runs git worktree add in the background. Name the pane, choose a base branch, and Pane handles the rest. Deleting a pane runs git worktree remove. You never type either command.

What isolation means

No shared files. Each pane writes to its own directory on disk. Agents can’t see or conflict with each other’s changes.
Separate .env. Each worktree reads its own environment file, so panes can have different credentials or feature flags.
Independent branches. Merging one pane to main doesn’t affect any other pane.
Parallel safe. Run five agents at once. They operate in completely separate trees.

Sidebar status cues

Pane’s sidebar is built for a lot of parallel work without turning into visual noise.

Pinned panes stay newest-first. Pin a pane and it rises to the top of the Pinned section; older pins drift downward.
Pinned navigation stays scoped. If you open a pane from Pinned, ⌘+↑/↓ on macOS or Ctrl+↑/↓ on Windows/Linux cycles through the pinned list. Open from Repositories and the same shortcut follows repository order.
Active work breathes. Pane names subtly breathe while a terminal is producing output.
Finished-elsewhere panes are marked. If a pane finishes while you’re looking elsewhere, its name gets a dashed blue underline until you click into it.
Sections collapse. Click Pinned or Repositories to hide that section when the sidebar gets too busy; open it again when you need the list back.

Archive marks a pane as archived and hides it from the active list. The git worktree and branch remain intact — you can revisit, inspect the diff, or restore it later.

Delete is permanent. The worktree directory is removed from disk and the branch is deleted. Use this when you’ve already merged or abandoned the work.

When in doubt, archive.

Pane creates each worktree in a sibling directory next to your project root. For a project at ~/code/myapp, a pane named add-login would be at ~/code/myapp-pane-add-login.

This keeps all worktrees close to the origin repo while ensuring they never share working files. Each directory is a fully independent checkout of the repository.