You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Git WorktreesArea: what it touches
ImprovementsKind: in v2.1.274,
ImprovementsSection of the release
What
When Claude Code refuses to remove a git worktree because of nested repositories, it used to report two separate reasons internally (nested_repositories and nested_unverified). These are now merged into a single "submodule" case, with wording that tells apart a worktree holding a separate git repository, which should be moved or deleted, from a submodule whose state can't be verified, which needs a manual check.
Why
This gives clearer, more consistent guidance when a worktree removal is blocked by nested repository content, telling the user directly whether they need to move or delete something versus check it manually.
