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.227 Home All releases ←olderv2.1.226 v2.1.228newer→
Claude Code v2.1.227

claude rm tells you which session is holding a directory

You'll notice
Useful3 Signal1
CLI

When claude rm is blocked, it names the session holding the directory and how to stop it.

claude rmclaude stop
What

When removal fails because a directory is still in use, the error now names the cause and tells you to exit the Claude Code session using it, or run claude stop <id> if it is a background session, then retry.

Details
  • Adds an "occupied" failure case alongside the existing removal errors, with the blocking session shown above the hint.
Evidence

exit the Claude Code session using that directory (shown above; or 'claude stop <id>' if it is a background session), then run 'claude rm

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.227 →