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.225 Home All releases ←olderv2.1.224 v2.1.226newer→
Claude Code v2.1.225

Background job state keeps respawn flags, and non-allowlisted tokens are stripped

Under the hood
Useful2 Signal0
Elsewhere

Background jobs now save the flags needed to relaunch them, dropping any unrecognised flags with a warning.

What

Persisted background job state now carries the flags needed to respawn a job, with unknown flag tokens filtered out before they are written.

Details
  • the job-state writer persists respawnFlags alongside the fields it already rewrites
  • the schema defaults respawnFlags to an empty list and filters its contents against an allowlist
  • dropped tokens produce a warning naming them
Evidence

[jobs] stripped non-allowlisted respawnFlags token(s) from persisted job state:

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.225 →