{"version":"2.1.228","anchor":"subagent-messages-no-longer-count-as-turns-in-tee-d-stream-j","canonical_anchor":"subagent-messages-no-longer-count-as-turns-in-tee-d-stream-j","heading":"Subagent messages no longer count as turns in tee'd stream-json output","tier":"notice","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/subagent-messages-no-longer-count-as-turns-in-tee-d-stream-j","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Subagent messages no longer count as turns in tee'd stream-json output\n\nSubagent chatter in the JSON output stream no longer counts as a new turn.\n\n**What**\n\nIn the JSON event stream written to stdout for external observers, user and assistant events produced by a subagent are now marked as such. The supervisor that tracks turn boundaries skips marked events, so a subagent talking no longer opens a follow-up turn or resets idle and activity tracking.\n\n**Details**\n\n- The marker is applied to events that carry a parent tool-use id, meaning they came from a tool-spawned subagent rather than the main conversation.\n- Both the code that adds the marker and the guard that ignores it are new.\n\n**Evidence**\n\n`from_subagent`\n\n- Area: SDK\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}