Claude Code v2.1.225 ·
Background job state keeps respawn flags, and non-allowlisted tokens are stripped
Background jobs now save the flags needed to relaunch them, dropping any unrecognised flags with a warning.
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
ImprovementsKind: in v2.1.225,
ImprovementsSection of the release
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 →
