crossSessionInbound accepts accept, hold or refuse for messages arriving from your other sessions.
What's wrong with this entry?
A settings key controlling what happens when another of your Claude Code sessions sends this one a message. Values are accept, hold and refuse. Left unset, a message is delivered automatically only when the sending session's permission mode is in the same class as yours, and is otherwise held for you to approve.
- Held and refused messages produce user-facing text naming the setting, for example
Your "crossSessionInbound" setting is "hold".
{ "crossSessionInbound": "refuse" }crossSessionInbound
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.
-
v2.1.225
Held peer messages now say which settings tier held them
Both mention cross inbound
-
v2.1.248
Settings validation checks crossSessionInbound
Both mention cross inbound
-
v2.1.248
Bad
crossSessionInboundvalues are now named where they surfaceBoth mention cross inbound