Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
WorktreesArea: what it touches
Internal ChangesKind: in v2.1.281,
Internal ChangesSection of the release
Unclear The finding does not say what you see differently once the check runs for hook-based worktrees.
What
A worktree is a separate working copy of your repository that Claude Code can work in. When you leave one and choose to keep it, Claude Code now always counts the files that changed and the commits that were made.
Before, this count was skipped for hook-based worktrees that had an original changeset recorded. A hook-based worktree is one created by a hook, which is a script you configure to run at certain moments, rather than by git. The skip condition was n.action === "keep" && r.hookBased === !0 && r.originalChangeset !== void 0. It is now r.action === "keep" && !1, which is always false, so the counting step xo(h, n) always runs.
Why
Hook-based worktrees now get the same count of changed files and commits as git worktrees when you keep them. The count feeds the record Claude Code makes when a worktree is kept, so nothing changes in how you keep or remove a worktree.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say what you see differently once the check runs for hook-based worktrees.
