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

Held peer messages now say which settings tier held them

You'll notice
Useful3 Signal0
Cross-Session Messaging

When a cross-session message is held, you now see whether org, repo or local settings did it.

crossSessionInbound
What

When an inbound cross-session message is held by an explicit setting, the notice names the settings layer responsible instead of giving a single generic cause.

Details
  • the old single hold cause "explicit-setting" was replaced by source attribution, including managed-setting
  • policy settings render "Your organization's managed settings set \"crossSessionInbound\" to \"hold\"."
  • project and local settings render "This repository's settings set \"crossSessionInbound\" to \"hold\" (your own \"accept\" cannot override a repo tightening)."
  • a WeakMap holds the last-reported cause so a notice is re-emitted only when the cause changes
Evidence

managed-setting

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