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

Deleting a background job keeps a directory a live session is sitting in

You'll notice
Useful4 Signal2
Background Jobs

Deleting a background job won't delete a directory another live session is using.

What

Job deletion now reports an "occupied" outcome instead of removing the worktree when it is the working directory of a live process. The message distinguishes a session you backgrounded from this window, a background session with a job id, and a bare process id and kind.

Evidence

deleteJob: ${c} is the working directory of a live session (pid ${m.pid}, ${m.kind})

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 →