Claude Code v2.1.225 ·
Held peer messages record their hold cause on re-evaluation
Queued messages from other sessions now report why they are still being held.
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
Cross-Session MessagingArea: what it touches
Internal ChangesKind: in v2.1.225,
Internal ChangesSection of the release
What
Re-running the inbound policy over queued cross-session messages now reports why each still-held message is held.
Details
- the hold cause, which may have changed since the message arrived, is passed to a listener along with the current queue depth
- refused messages additionally fire a drop callback
Evidence
[cross-session-inbound] dropped
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.225 →
