What
An unacceptable crossSessionInbound value now produces its own settings error rather than passing silently, and a further check on the same setting can also mark the file invalid.
Evidence
"crossSessionInbound"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundlecrossSessionInbound
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Message your other Claude Code sessions touched a line naming crossSessionInbound after this was published.
To see which value applies, follow the `crossSessionInbound` precedence rules in the [settings reference](/docs/en/settings-reference#crosssessioninbound).cross-session-messaging see the edit
Confirmed since
Anthropic's documentation has since written up crossSessionInbound, on Error reference.
| `"crossSessionInbound" must be one of "accept", "hold", "refuse"` | [Configuration warnings](#crosssessioninbound-must-be-one-of-accept-hold-refuse) |errors see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up crossSessionInbound, on Error reference.
Anthropic's release notes agree
Fixed an invalid crossSessionInbound value being silently ignored: it now warns and holds cross-session messages (user settings) or refuses…