Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.239 Home All releases ←olderv2.1.238 v2.1.240newer→
Claude Code v2.1.239

Second emit site for the agent-spawn event, which still has no listener

Under the hood
Useful1 Signal4
Subagents Notable

Starting an async agent now announces itself on an internal channel that nothing in this build listens to.

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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.239 →