Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.275 ·

Orphaned backgrounded tasks get auto-aborted and quietly parked

Background tasks left running after their owning agent disappears are now automatically stopped

Nothing to try yet In Development
JSON All of v2.1.275
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Background TasksArea: what it touches
In DevelopmentKind: in v2.1.275,
In DevelopmentSection of the release
What

When a task running in the background loses its owning agent (the agent that started it no longer exists), Claude Code now detects this and automatically stops it, rather than letting it keep running indefinitely. This only happens for tasks that are actually running in the background, have a way to be cancelled, and have already produced at least one successful (non-error) response. Once stopped this way, the task is marked as notified and "quietly parked."

A related change also adjusts how the app decides whether a completed background task still needs to stay alive, based on whether it's backgrounded and not already in another state.

Why

This prevents orphaned background tasks from consuming resources or running forever after the thing that started them is gone, while still preserving whatever useful output they had already produced.

Read from
Feature flag
tengu_zinc_harbor Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.275: off

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.275. It isn't a statement about your account. What a flag value here can and cannot tell you

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_zinc_harbor

See this entry in the whole of v2.1.275 →

Feedback