Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.293 ·

Tasks Claude is waiting on are no longer treated as background tasks

A change in a task's awaited flag now triggers a background_tasks_changed message, and awaited tasks are no longer tracked as background work

Group of 2 You'll notice Improvements
JSON All of v2.1.293
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
AgentsArea: what it touches
ImprovementsKind: in v2.1.293,
ImprovementsSection of the release

What

A background task is work Claude Code keeps running while the conversation carries on, such as a subagent (a helper agent started for one job). Some of these tasks are ones the session is actively waiting on, marked with an awaited field.

  • A change in a task's awaited field now sends a background_tasks_changed system message. Before, change detection only looked as far as the ambient field.
  • When system messages are handled, background_tasks_changed entries and task_started messages are now skipped if awaited is true. Before, every task was passed on to be tracked, or every task not marked is_backgrounded:false.
  • Agent launches now also pass canContinueAgent: !0, meaning true.

Why

Tasks the session is waiting on are no longer counted as background work. Programs built on the SDK (the kit for running Claude Code from your own code) see awaited changes as they happen, and what shows up as background work in the interface may change.

See this entry in the whole of v2.1.293 →

Feedback