A failed peer listing is now reported as a failure rather than an empty roster.
What's wrong with this entry?
When Claude Code cannot list the other sessions it can reach, the failure is now recorded as a failure instead of coming back as an empty roster. This matters for the ListAgents tool, which only records what the model saw when the listing actually succeeded.
- Failure is set when auth preparation throws, when the list request throws, or when the server returns a non-200 status.
- Logs
[bridge:peers] auth prep failed:,[bridge:peers] list request failed:and[bridge:peers] list failed. - The population fetch carries the failure flag through and logs a "FAILED, not recordable" marker.
[bridge:peers] auth prep failed:
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