{"version":"2.1.292","anchor":"background-tasks-gain-run-ids-and-parent-task-ids","canonical_anchor":"background-tasks-gain-run-ids-and-parent-task-ids","heading":"SDK background task events now carry a run ID and a parent task ID","tier":"notice","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/background-tasks-gain-run-ids-and-parent-task-ids","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### SDK background task events now carry a run ID and a parent task ID\n\nSDK task notifications gain `runId`, and the background tasks changed event now includes `parent_task_id`\n\n**What**\n\nThe SDK lets programs drive Claude Code and listen to what it does. Background tasks are jobs Claude Code keeps running while the conversation goes on. Two fields are new in the events the SDK sends about them:\n\n- `runId` on task notifications. It identifies one run of a task, and every task event from that run carries the same value.\n\n- `parent_task_id` on the `background_tasks_changed` system event. It names the task that started this one. Claude Code now also treats a change in this field as a change worth reporting.\n\n**Why**\n\nPrograms built on the SDK can now group the events that belong to a single run. They can also tell which background task was started from inside another.\n\n- Area: SDK\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}