{"version":"2.1.318","anchor":"tool-use-ids-carried-into-nested-contexts-and-agent-events","canonical_anchor":"tool-use-ids-carried-into-nested-contexts-and-agent-events","heading":"Agent status events can now carry the id of the tool call that started them","tier":"notice","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/tool-use-ids-carried-into-nested-contexts-and-agent-events","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Agent status events can now carry the id of the tool call that started them\n\nWhen a check is on, agent status events include the id of the enclosing tool call, and that id is passed to the work it starts\n\n**What**\n\nA tool call is one action Claude takes, and each has an id. When a certain check is on, Claude Code now passes that id into the work the tool call starts. Status events from agents (separate Claude workers started to handle part of a task) now include `enclosingToolUseId` when it is known. Before, nothing was sent there.\n\n**Why**\n\nThis looks like groundwork for linking tool calls made inside other tool calls back to the call that started them.\n\n- Area: SDK\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}