worktree-map

worktree-map opens a pane in Claude Code that lists every git worktree of the repository you are working in: where it lives, the commit its HEAD points at, its branch, and whether it is locked. It is for keeping track of parallel work, such as several sessions each running in a worktree of its own, without leaving the conversation.

It is one of 70 small mods in Yash Thakker’s awesome-claude-code-mods collection, each installed on its own.

Install

Needs Claude Code 2.1.287 or later, plus Git on your PATH.

claude plugin marketplace add whyashthakker/awesome-claude-code-mods
claude plugin install worktree-map@awesome-claude-code-mods

Run /reload-plugins in an open session, then /worktree-map. Press r to read the worktrees again, Tab and Enter to use the controls, and Esc to close the pane.

How it works

Each time you open the pane or press r, the mod runs one read-only command, git --no-pager worktree list --porcelain, in the session’s working directory, with a 10-second timeout. The pane shows git’s output as it comes: a worktree, HEAD and branch line for each worktree, plus a locked line on a locked one. When git fails, for example outside a repository, the pane shows git’s error instead.

Nothing runs in between. The mod writes nothing, keeps nothing between sessions, and makes no network or model calls.

Limitations

• The list is a snapshot. It does not follow changes on its own: press r after adding or removing a worktree.
• It always reads the repository of the session’s working directory. The command shows a [path] hint, but version 1.0.0 ignores the argument.
• Output past 9,000 characters is cut.
• The pane draws in the terminal and in the Desktop app’s Code tab, both covered by the author’s tests, but not in claude -p or the VS Code chat panel.