Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.247 Home All releases ←olderv2.1.246 v2.1.248newer→
Claude Code v2.1.247

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

You'll notice
Useful2 Signal2
Git Safety

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

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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.247 →