Git Worktrees

You're mid-feature when an urgent hotfix lands. The standard git workflow forces you to stash your work, switch branches, fix the bug, switch back, and pop the stash — losing your editor state, your scrollback, and your context every time. Git Worktrees let you spin up linked working copies of the same repo, one per branch, each with its own files and terminals. The new Worktrees tab in the Git Client shows every worktree as a card with its branch name, dirty state badge, lock state, colored dot, and the list of terminals running inside it. Click "+ Terminal" on a worktree card and the Add Terminal dialog opens with that worktree pre-selected — and the picker defaults to whichever worktree your currently focused terminal is using, so opening a new tab in the same worktree is a single click. Lock worktrees to protect important ones from accidental removal, prune stale worktrees in one click when you delete a folder by hand, and right-click any commit in the visual git graph to spin up a new worktree from that exact revision — perfect for hotfixes off an old release. Every git command in the Git Client now runs against the active worktree, not just the project root, and dirty-state badges poll every five seconds so editing a file in one worktree shows up immediately in the others. Switching is now a status-bar affordance rather than a trip through Git Client: the active checkout shows its colour and its primary, locked and dirty marks, and picking another brings forward a terminal that already belongs to it instead of stranding you on a tab from a different tree — the most common way a command ends up running in the wrong checkout. A worktree with no visible terminals says so and offers to add one, rather than showing a leftover pane from somewhere else.