{"version":"2.1.239","anchor":"second-emit-site-for-the-agent-spawn-event-which-still-has-n","canonical_anchor":"second-emit-site-for-the-agent-spawn-event-which-still-has-n","heading":"Second emit site for the agent-spawn event, which still has no listener","tier":"internal","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/second-emit-site-for-the-agent-spawn-event-which-still-has-n","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Second emit site for the agent-spawn event, which still has no listener\n\nStarting an async agent now announces itself on an internal channel that nothing in this build listens to.\n\n**What**\n\nThe path that starts an async agent now announces it on the same internal channel the Agent tool already used, carrying the agent id, agent type, parent agent id and task registry. Nothing subscribes to that channel anywhere in the build, so the two emits go nowhere.\n\n**Details**\n\n- The channel is `agentSpawned`: one declaration, two emits, zero subscribers, in both v2.1.238 and v2.1.239.\n- Its neighbouring channels for evicted tasks and settled agents do have consumers, so this one being unread looks like groundwork rather than an oversight.\n\n**Evidence**\n\n`agentSpawned`\n\n- Area: Subagents\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}