Skip to content

Why zap chose that status

cloudranger edited this page Nov 14, 2026 · 1 revision

To see how zap picked a status, run zap explain:

zap explain .claude/worktrees/auth
zap explain shows the auth worktree is merged because the squash check passed

checks are the tests zap runs to pick a status, in order. The first ✓ decides. Here the branch was squash-merged, so its commits are not in main (ancestor and cherry fail), but merging it would change nothing (squash passes). That makes it merged.

facts are what zap found in the folder: uncommitted changes, locks, size and dates.

A merged worktree zap still keeps

merged means the branch's work is in main. Before zap removes the folder, it also runs the safety checks. This Cursor worktree is merged:

zap explain on the Cursor worktree in ~/dev/api shows it as merged

but it holds a .env file that git ignores, and a clean would delete that file, so zap keeps the worktree. zap clean --dry-run and the picker both give the reason:

keep: holds ignored .env, which would be lost

--json prints the same report for scripts.

Next: Opt a repository in

Clone this wiki locally