Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
SubagentsArea: what it touches
Internal ChangesKind: in v2.1.239,
What probably matters to youSection of the release
Two sites now emit an agent-spawn event carrying agent id, type, parent and task registry, with no subscriber anywhere.
What
The 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.
Details
The channel is agentSpawned: one declaration, two emits, zero subscribers, in both v2.1.238 and v2.1.239.
Its neighbouring channels for evicted tasks and settled agents do have consumers, so this one being unread looks like groundwork rather than an oversight.
Evidence
agentSpawned
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
