Messages a sub-agent sends elsewhere now say they went under the session's address.
What's wrong with this entry?
When a sub-agent sends a message to another session, the tool result now explains that the message went out under the session's address rather than the agent's, and where any reply will land. It is on for everyone on this build, with no flag.
- Applies to both delivery paths: the inter-session bridge and the local socket path.
- Two wordings: a one-way form used when the bridge only has a one-way route, or when the socket path finds no messaging socket of its own, and the default form.
- The user-visible display string is the parenthetical variant.
; sent under this session's address: any reply will be delivered to this session's main conversation, not to this agent
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.
-
v2.1.234
Messages injected by a host are classified separately from peer messages
Both mention cross
-
v2.1.234
Cross-session control requests check ids more carefully
Both mention cross
-
v2.1.234
Notice acks now wait for the record to persist
Both mention cross