{"version":"2.1.293","anchor":"awaited-flag-in-background-tasks-changed","canonical_anchor":"awaited-flag-in-background-tasks-changed","heading":"Tasks Claude is waiting on are no longer treated as background tasks","tier":"notice","area":"Agents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/awaited-flag-in-background-tasks-changed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Tasks Claude is waiting on are no longer treated as background tasks\n\nA change in a task's awaited flag now triggers a background_tasks_changed message, and awaited tasks are no longer tracked as background work\n\n**What**\n\nA 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.\n\n- 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.\n\n- 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`.\n\n- Agent launches now also pass `canContinueAgent: !0`, meaning true.\n\n**Why**\n\nTasks 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.\n\n- Area: Agents\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}