Every pane is an isolated workspace — its own branch, its own directory, its own terminal.

Status

Each pane carries a live status indicator:

initializing Cloning the worktree and checking out the branch.

running An agent is actively executing in the terminal.

waiting The terminal is idle — agent has paused or finished a step.

completed Work is done. Ready to review and merge.

error The agent exited with an error. Check the terminal output.

stopped Manually stopped. The worktree is still intact.

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.

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.