Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.238 Home All releases ←olderv2.1.237 v2.1.239newer→
Claude Code v2.1.238

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

You'll notice
Useful3 Signal3
Cross-Session Messaging

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

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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.238 →