{"version":"2.1.305","anchor":"subagent-metadata-sidecar-mirrored-to-the-event-stream-stor","canonical_anchor":"subagent-metadata-sidecar-mirrored-to-the-event-stream-stor","heading":"Subagent details can also be sent to a session's event stream","tier":"internal","area":"Subagents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/subagent-metadata-sidecar-mirrored-to-the-event-stream-stor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Subagent details can also be sent to a session's event stream\n\nSaved details about a subagent can now also be sent as an event on the session's event stream, not only written to a file\n\n**Unclear.** It is not stated what decides whether subagent details are sent to the event stream.\n\n**What**\n\nA subagent is a helper agent Claude starts to work on part of a task. Claude Code saves details about each subagent in a small file next to the session (`agent-<id>.meta.json`). It now records which session the file belongs to and, when a setting allows it, also sends those details as an event on the session's event stream (the live feed of what the session is doing). Claude Code records whether each send succeeded, was held back, or failed.\n\nBefore, the details were only written to the file.\n\n**Why**\n\nSubagent state can reach people viewing the session remotely, not only the machine running it.\n\n- Area: Subagents\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}