{"version":"2.1.219","anchor":"sub-agent-stream-messages-keep-their-own-parent-tool-id","canonical_anchor":"sub-agent-stream-messages-keep-their-own-parent-tool-id","heading":"Sub-agent stream messages keep their own parent tool id","tier":"notice","area":"Sub-Agents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/sub-agent-stream-messages-keep-their-own-parent-tool-id","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### Sub-agent stream messages keep their own parent tool id\n\nOutput from nested tool calls inside sub-agents is now attributed to the right call.\n\n**What**\n\nStreamed tool events re-enqueued from a sub-agent now carry the parent tool use id from the event itself, so nested tool output is attributed to the right call.\n\n**Details**\n\n- the id on the event is preferred, with the enclosing tool use id only as a fallback\n- previously output from nested tool calls could be reattributed to the outer tool\n\n**Evidence**\n\n`parentToolUseID`\n\n- Area: Sub-Agents\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}