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.224 Home All releases ←olderv2.1.223 v2.1.225newer→
Claude Code v2.1.224

Cross-session messages from a coordinator are now delivered by default

Use it now
Useful4 Signal4
Cross-Session Messaging Notable

Task notifications from a coordinator session now arrive automatically unless you set crossSessionInbound to refuse or hold.

crossSessionInboundrefusehold
What

Messages arriving from another session are now sorted into three classes, and a new "coordinator" class (a task notification that carries a peer send-message) is delivered unless you explicitly set crossSessionInbound. Set it to refuse to reject them or hold to buffer them; with no setting at all, coordinator messages are accepted outright.

Details
  • The other two classes are peer messages, which follow the existing peer policy, and ungated messages.
  • hold puts coordinator messages into the same hold queue as peer messages; the queue drops its oldest entry when full.
  • Only an explicit crossSessionInbound value can hold or refuse this class, so an unset config means accept.
Evidence

Your "crossSessionInbound" setting is "hold".

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