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.280 ·

Status tracking gains an 'open' field for running vs stalled vs unknown state

Task and remote status responses now include an 'open' field marking whether an operation is stalled, still running, or of unknown delivery

Group of 2 Under the hood Internal Changes
JSON All of v2.1.280
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Background TasksArea: what it touches
Internal ChangesKind: in v2.1.280,
Internal ChangesSection of the release

What

Status objects for timed or capped remote/background operations now include a new open field:

  • A status object used for tracking timed/capped operations now sets open: "stalled" when a request isn't a probe and hasn't been 'taken back,' in addition to its existing taken-back-based branching.
  • A still_running status response now includes open set to either "still_running" (when the operation is literally still running) or "delivery_unknown" otherwise, alongside the existing code/message/host fields.

Why

This gives a clearer, explicit signal for distinguishing an operation that's genuinely still running from one that's stalled or whose delivery status just isn't known, instead of leaving that ambiguous.

See this entry in the whole of v2.1.280 →

Feedback