Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.308 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.246 ·

Restarting a background job no longer races a spawn already under way

Restarting a background job waits for any spawn already running instead of starting a second.

You'll notice Bug Fixes
JSON All of v2.1.246
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Background TasksArea: what it touches
Bug FixesKind: in v2.1.246,
Bug FixesSection of the release
What

Respawning a background or fleet session now waits for any spawn already in flight for that job rather than starting a second one. If that spawn failed and left nothing running, the respawn stops with the failure reason in_flight_spawn_failed and queues the initial prompt instead of double-spawning.

Evidence

in_flight_spawn_failed

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

Feedback