Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.238entry #73

Claude Code v2.1.238 ·

Messages to another session check the recipient first, and each session reports its own inbound state

Messaging another session checks the recipient first and gives a specific reason when refused.

You'll notice New Features
JSON All of v2.1.238
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Cross-Session MessagingArea: what it touches
New FeaturesKind: in v2.1.238,
New FeaturesSection of the release
What

Sending to another session by address, cloud name or remote-control name now runs a recipient check up front, with its own denial wording and telemetry class instead of the generic unreachable-session message. Sessions also report their own inbound availability upstream.

Details
  • The check reads the target's crossSessionInbound setting (accept, hold, refuse); when it is off, the send is denied with a distinct decision reason.
  • Each session mirrors cross_session_inbound as available or unavailable, with new last-reported and last-known fields and a reseed path so the value is re-sent after the connection handle changes.
  • The check itself is unconditional on this build.
Evidence

target session reports it cannot receive cross-session messages

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.238 →

Feedback