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.248 Home All releases ←olderv2.1.247 v2.1.250newer→
Claude Code v2.1.248

Killed background tasks leave a record behind

You'll notice
Useful3 Signal2
Background Tasks

Killing a background task keeps a record and its output file instead of losing both.

What

Killing a background bash task now records a snapshot of it against the owning agent before cleanup, with outcome "killed", no exit code, and the output file path kept, so the output is still reachable afterwards.

Details
  • Skipped for tasks of kind "monitor".
  • Also depends on a runtime check whose condition is not visible from the built code.
Evidence

rememberBashTaskSnapshot

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