Claude Code in git worktrees, without making them by hand.
Kanzai gives every card its own git worktree and branch. Drag a card into Development and Claude Code starts in a fresh worktree. Drag it into Approved and Kanzai merges the branch back, one card at a time.
Start using Kanzai for free. No account required.
macOS · Windows x86_64 · Linux AppImage x86_64 · Linux deb x86_64 · arm64 builds
A screenshot of the Files view. The diff for a task branch sits beside its file list, a comment is anchored to a changed line, and three drafted comments are ready to go back to the session as one message.
Two agents in one checkout overwrite each other. Worktrees fix that, one command at a time.
Claude Code edits the files in the directory it starts in. Start two agents in the same checkout and they write to the same files, run tests against each other's half-finished changes, and commit onto the same branch.
A git worktree solves that. It is a second working directory on its own branch, sharing the one repository, so each agent gets a folder nobody else writes to. By hand, though, every task means git worktree add with a new path and a new branch, installing dependencies in the fresh folder, and starting Claude Code there. Afterwards, each branch has to be merged back in the right order, and each worktree removed.
Kanzai does the bookkeeping. Starting a card makes its worktree and branch. Dragging it into Approved merges the branch back, one card at a time. Done removes the worktree.
HOW KANZAI SOLVES IT
A worktree for every card
Starting a card gives it its own git worktree, on a branch named after the card and forked from the base you picked. A card that spans several repos gets a worktree in each.
Ready to build
A repo can name a setup line, such as npm install. Kanzai runs it once in every new worktree and waits for it, so the agent never starts in a tree that cannot build.
Review the worktree's diff
The Files tab shows what changed in the card's worktree since its base. Comment on lines and send the comments back to the same Claude Code session.
Merged back one at a time
Approved is a merge queue. Branches merge one at a time, in column order, in a worktree Kanzai keeps for merging, so you never check out a branch for it. Uncommitted work is committed by its agent first.
Conflicts caught, never forced
A waiting card shows how far its branch has fallen behind and offers a rebase. A conflicting merge is aborted, and a conflicting rebase goes to the agent that wrote the change.
Cleaned up in Done
Done removes the worktree and keeps the branch. If the worktree still has uncommitted changes, Kanzai shows them and lets you decide instead of throwing them away.
HOW TO RUN CLAUDE CODE IN GIT WORKTREES
Install Kanzai
Download it for macOS, Windows or Linux. It is free and needs no account. Have Claude Code installed and signed in.
Add your repo
Add your local checkout to a project. If a fresh checkout needs something before it builds, give the repo a setup line such as npm install.
Start a card
Write the task, pick the branch to fork from, and drag the card into Development. Kanzai makes the worktree and branch, and Claude Code starts inside it.
Approve to merge
Read the diff in Review. Drag the card into Approved and the queue merges its branch into the base. The card moves to Done, and its worktree is removed.
- Native app for macOS, Windows and Linux
- Runs locally, with no account and your data in one file
- Runs the real Claude Code, Codex, Grok Build, Antigravity and OpenCode CLIs
- Use your Claude or ChatGPT plan, xAI login or Google sign-in; only OpenCode may need an API key
- Works with any Git host
Stop typing git worktree add.
Give every Claude Code task its own git worktree and branch, and let Approved merge them back one at a time. Keep using the subscription you already pay for.
The button picks x86_64 for Windows and Linux. On arm64 hardware, take the arm64 build.