{"version":"2.1.248","anchor":"bad-crosssessioninbound-values-are-now-named-where-they-surf","canonical_anchor":"bad-crosssessioninbound-values-are-now-named-where-they-surf","heading":"Bad crossSessionInbound values are now named where they surface","tier":"notice","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/bad-crosssessioninbound-values-are-now-named-where-they-surf","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Bad `crossSessionInbound` values are now named where they surface\n\nA bad crossSessionInbound value is now named directly instead of a generic settings complaint.\n\n**What**\n\n`crossSessionInbound` is the setting that controls whether messages sent from other Claude Code sessions are accepted. When a settings file gives it a value that is not recognised, incoming cross-session messages are held, and both the place that holds them and the managed-settings validator now say so by name rather than falling back to a generic reason or a generic schema complaint.\n\n**Details**\n\n- The hold reason is labelled `invalid-setting`, and the accompanying settings warning names the offending file.\n- Two texts ship for the held state: a short one for the status surface, and a longer one that lists which values are legal.\n- Before this, an unparseable value fell through to the default explanation for held messages.\n- In administrator-managed settings, the validation report calls out a bad `crossSessionInbound` value alongside the existing unknown-key and `mcpServers` messages.\n\n**Evidence**\n\n`A settings file has an unrecognized \"crossSessionInbound\" value (the settings warning names the file); messages are held while it is present`, `A settings file has an unrecognized \"crossSessionInbound\" value (see the settings warning), so messages are held while it is present.`, `crossSessionInbound: `\n\n- Area: Settings\n- Names: `crossSessionInbound`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}