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

Sessions can advertise that they will not accept cross-session messages

You'll notice
Useful3 Signal3
Cross-Session Messaging

Sessions that block incoming messages are now labelled, and sending to one is refused up front.

What

When you list other sessions, ones that have turned off incoming cross-session messages are now labelled as such, and an attempt to message them is refused before anything is sent rather than failing later as an unreachable session.

Details
  • The listing marks a session unavailable from the server-side metadata field cross_session_inbound, and the row is rendered with a short label.
  • The permission path denies the send and records the failure as errorClass: "recipient_gate_off".
  • No flag: it depends on the peer's metadata being present in the listing. A warm-cache lookup that throws falls open to "unknown", so the send is attempted as before.
Evidence

can't receive cross-session messages (off in that session)

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 →