Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.225 ·

Held cross-session messages are now settled as expired at shutdown

Quitting now settles pending peer messages as expired so the sending session gets a definite answer.

You'll notice New Features
JSON All of v2.1.225
You'll noticeTier: 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
New FeaturesKind: in v2.1.225,
New FeaturesSection of the release
What

When Claude Code exits, peer messages that were being held in the cross-session inbound queue are answered as expired instead of being abandoned, so the sending session gets a definite result.

Details
  • A shutdown hook drains the hold buffer and settles every still-held peer message with an expired status, logging how many were settled
  • The drain is raced against a grace period of up to 750 ms before shutdown continues
  • Once shutdown has begun, a late peer message is refused rather than parked, recording peer_inbound_gate / shutdown_expired telemetry
  • Unix-socket messaging server teardown now also destroys open connections and unlinks the socket file before awaiting the drain
  • A new lookup lets the headless expiry path read a message's hold cause
Evidence

[cross-session-inbound] shutdown: settling ${e.length} still-held peer message(s) as expired, shutdown: settling , [cross-session-inbound] shutdown: not parking a late peer message \u2014 settled as expired:

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 →

Feedback