If checking whether a peer session can receive messages fails, you get the unconfirmed-delivery caveat.
What's wrong with this entry?
When the check for whether a peer session can receive cross-session messages fails outright, Claude Code logs the failure and treats that session as not having reported support, so the send carries the same unconfirmed-delivery caveat for the model and the shorter note on screen.
- The log line is
[agents:cloud] warm inbound-report lookup failed. - No gate: a lookup failure always falls back to the cautious wording rather than assuming delivery worked.
[agents:cloud] warm inbound-report lookup 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