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

Background worker that never starts is reported as a crash

You'll notice
Useful2 Signal1
Background Tasks

A background worker that dies before starting is reported as a crash, not silence.

What

A worker that never became ready and exited for a specific known cause is now classified as crashed rather than passing quietly, so failed background work shows up instead of disappearing.

Details
  • The new condition sits alongside the existing bad working directory, repeated attempt and last exit cause checks, any of which force the crashed outcome.
  • Feeds the existing tengu_bg_worker_exit telemetry.
Evidence

tengu_bg_worker_exit

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 →