You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Cross-Session MessagingArea: what it touches
ImprovementsKind: in v2.1.238,
ImprovementsSection of the release
What
Messages held for approval between sessions gained two new outcomes. If policy refuses a message after it is approved, the sender gets a refused receipt instead of "expired" or "denied", and a released message is re-checked against the receiving session's inbox guard, which can now drop it.
Details
The recipient sees a warning when the inbox guard had no room for a released message.
The sending session's Claude gets delivery notices for the refused and dropped cases, telling it not to resend.
On the wire, refused is sent as status: "expired" with status_detail: "refused"; drops add drop_reason and dropped_msg_ids.
Part of the existing cross-session peer feature, which the code still describes as having a kill switch and a per-session opt-out.
Evidence
The recipient session is not accepting cross-session messages (the feature is off there, or a setting or policy there refuses them); your message was not delivered to its Claude.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
