{"version":"2.1.293","anchor":"agent-notification-and-subagent-task-payloads-gain-subagent","canonical_anchor":"agent-notification-and-subagent-task-payloads-gain-subagent","heading":"Task payloads say which agent runs a task and whether it is awaited","tier":"use","area":"Agents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/agent-notification-and-subagent-task-payloads-gain-subagent","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Task payloads say which agent runs a task and whether it is awaited\n\nTask events and task lists gain subagent_type, naming the agent type or main-session, and an awaited flag\n\n**What**\n\nA task is a piece of work Claude Code tracks, such as a subagent (a helper agent started for one job) running in the background. Task information sent to programs built on the SDK, the kit for running Claude Code from your own code, now carries two more fields.\n\n- `subagent_type`, an optional field naming the agent type of a `local_agent` task, such as `\"general-purpose\"` or a custom agent's name, or `\"main-session\"` for a backgrounded main session. It is not set on other tasks. It is also added to the task list schema.\n\n- `awaited`, an optional flag on task-started and task-list entries, set to true when a `local_agent` has `awaitedByCaller === true`. Before, there was no such field.\n\nThe documentation no longer says that the payload carries ids only.\n\n**Why**\n\nPrograms built on the SDK can show which agent a background task is running, and can tell tasks the caller is waiting on apart from ones running on their own.\n\n- Area: Agents\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}