Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.247entry #138

Claude Code v2.1.247 ·

Worktree cleanliness checks and removal use the same pinned config, and removal aborts when unsure

Worktree cleanup aborts rather than deleting a tree whose state it cannot safely determine.

You'll notice Improvements
JSON All of v2.1.247
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Git SafetyArea: what it touches
ImprovementsKind: in v2.1.247,
ImprovementsSection of the release
What

The dirty-check (git status --porcelain) and the agent-worktree removal path now run with the same filter-neutralizing settings. If those settings cannot be applied, the worktree is treated as dirty or as a git error, and removal is aborted rather than deleting a tree whose state is unknown.

Details
  • The helper that builds the pinned arguments returns nothing on failure, and callers fall back to dirty/gitError.
  • Removal reports a new abort reason when cleanliness could not be established.
  • The tengu_worktree_removed event still carries changed_files and aborted.
Evidence

could not verify the worktree is clean (git status failed or repository git config unpinnable)

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.247 →

Feedback