Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

crossSessionInbound

setting gone documented JSON

A Claude Code settings key, read out of the shipped bundle. It was in the build from v2.1.224 and was gone by v2.1.284.

Choose whether Claude Code delivers messages from your other sessions, shows a notice without delivering them, or refuses them

Anthropic's own wording. Read off All settings, captured 2026-10-22.

First seen v2.1.224 7 Aug 2026
Last seen v2.1.283 25 Sep 2026, gone by v2.1.284
Builds50 / 149on this box, as of v2.1.308
Written about v2.1.224 first named in a changelog, 7 Aug 2026
v2.1.224in the build not in the build never minedv2.1.308

In the changelogs

10

Releases whose published page names crossSessionInbound.

  1. v2.1.271
    peer_message_hold: visibility into parked cross-session messages

    A new peer_message_hold event reports when a message from another session is parked instead of delivered, and how it's later resolved

    found in this entry's text, named in this entry

  2. v2.1.248
    Bad crossSessionInbound values are now named where they surface

    A bad crossSessionInbound value is now named directly instead of a generic settings complaint.

    named in this entry, found in this entry's text

  3. v2.1.248
    Settings validation checks crossSessionInbound

    A bad crossSessionInbound value now gives you a settings error instead of passing silently.

    named in this entry, found in this entry's text

  4. v2.1.238
    Messages to another session check the recipient first, and each session reports its own inbound state

    Messaging another session checks the recipient first and gives a specific reason when refused.

    found in this entry's text

  5. v2.1.225
    Held cross-session messages name managed or repo settings as the cause

    When a peer message is held, you now see whether org or repo settings caused it.

    found in this entry's text

  6. v2.1.225
    Held peer messages now say which settings tier held them

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

    named in this entry, found in this entry's text

  7. v2.1.224
    Cross-session messages from a coordinator are now delivered by default

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

    named in this entry, found in this entry's text

  8. v2.1.224
    New setting: crossSessionInbound

    crossSessionInbound accepts accept, hold or refuse for messages arriving from your other sessions.

    named in this entry, found in this entry's text

  9. v2.1.224
    Messages relayed between your own sessions are now labelled as such

    Messages relayed from your other sessions are now tagged as peer sends rather than looking like scheduled triggers.

    found in this entry's text

  10. v2.1.224
    Messages from other sessions can be held for your approval

    Messages from a session with a mismatched permission mode are held and shown with an approve/deny dialog.

    found in this entry's text

First cited

10

The earliest release whose published evidence quoted crossSessionInbound was v2.1.224, 7 Aug 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

ReleaseDateThe span that was quoted
v2.1.2247 Aug 2026The sender did not attest its permission mode and this session bypasses prompts. Review it below, or set "crossSessionInbound" to "accept".
v2.1.2247 Aug 2026Your "crossSessionInbound" setting is "hold".
v2.1.2247 Aug 2026crossSessionInbound
v2.1.2247 Aug 2026so the receive-side crossSessionInbound setting can apply to it
v2.1.2257 Aug 2026This repository's settings set "crossSessionInbound" to "hold" (a repo may only tighten, so your own "accept" cannot override it); remove the repo setting or exclude it with --setting-sources.
v2.1.2257 Aug 2026This repository's settings set "crossSessionInbound" to "hold" (your own "accept" cannot override a repo tightening).

4 further spans in the ledger name it. The list above is the earliest first and stops at 6.

Presence across releases

2
BuildsHow manyDatesReading
v2.1.224 – v2.1.28350 builds7 Aug 2026 → 25 Sep 2026 ◆in the build
v2.1.284 – v2.1.30823 builds28 Sep 2026 → 22 Oct 2026 ○not in the build

Build by build

73

One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.

BuildDateStateThe record behind it
v2.1.2247 Aug 2026·addedverdict: added
v2.1.2257 Aug 2026·presentverdict: present
v2.1.2268 Aug 2026·presentverdict: present
v2.1.22710 Aug 2026·presentverdict: present
v2.1.22811 Aug 2026·presentverdict: present
v2.1.22912 Aug 2026·presentverdict: present
v2.1.23113 Aug 2026·presentverdict: present
v2.1.23213 Aug 2026·presentverdict: present
v2.1.23314 Aug 2026·presentverdict: present
v2.1.23417 Aug 2026·presentverdict: present
v2.1.23518 Aug 2026·presentverdict: present
v2.1.23619 Aug 2026·presentverdict: present
v2.1.23719 Aug 2026·presentverdict: present
v2.1.23820 Aug 2026·presentverdict: present
v2.1.23921 Aug 2026·presentverdict: present
v2.1.24022 Aug 2026·presentverdict: present
v2.1.24122 Aug 2026·presentverdict: present
v2.1.24224 Aug 2026·presentverdict: present
v2.1.24324 Aug 2026·presentverdict: present
v2.1.24525 Aug 2026·presentverdict: present
v2.1.24625 Aug 2026·presentverdict: present
v2.1.24726 Aug 2026·presentverdict: present
v2.1.24827 Aug 2026·presentverdict: present
v2.1.25027 Aug 2026·presentverdict: present
v2.1.25128 Aug 2026·presentverdict: present
v2.1.25231 Aug 2026·presentverdict: present
v2.1.2571 Sep 2026·presentverdict: present
v2.1.2581 Sep 2026·presentverdict: present
v2.1.2592 Sep 2026·presentverdict: present
v2.1.2603 Sep 2026·presentverdict: present
v2.1.2614 Sep 2026·presentverdict: present
v2.1.2636 Sep 2026·presentverdict: present
v2.1.2658 Sep 2026·presentverdict: present
v2.1.2668 Sep 2026·presentverdict: present
v2.1.2679 Sep 2026·presentverdict: present
v2.1.26810 Sep 2026·presentverdict: present
v2.1.26911 Sep 2026·presentverdict: present
v2.1.27012 Sep 2026·presentverdict: present
v2.1.27114 Sep 2026·presentverdict: present
v2.1.27214 Sep 2026·presentverdict: present
v2.1.27315 Sep 2026·presentverdict: present
v2.1.27416 Sep 2026·presentverdict: present
v2.1.27517 Sep 2026·presentverdict: present
v2.1.27618 Sep 2026·presentverdict: present
v2.1.27718 Sep 2026·presentverdict: present
v2.1.27819 Sep 2026·presentverdict: present
v2.1.28022 Sep 2026·presentverdict: present
v2.1.28123 Sep 2026·presentverdict: present
v2.1.28224 Sep 2026·presentverdict: present
v2.1.28325 Sep 2026·presentverdict: present
v2.1.28428 Sep 2026·removedverdict: removed
v2.1.28529 Sep 2026·absent—
v2.1.28630 Sep 2026·absent—
v2.1.2871 Oct 2026·absent—
v2.1.2882 Oct 2026·absent—
v2.1.2893 Oct 2026·absent—
v2.1.2905 Oct 2026·absent—
v2.1.2916 Oct 2026·absent—
v2.1.2926 Oct 2026·absent—
v2.1.2937 Oct 2026·absent—
v2.1.2948 Oct 2026·absent—
v2.1.2958 Oct 2026·absent—
v2.1.2969 Oct 2026·absent—
v2.1.29914 Oct 2026·absent—
v2.1.30014 Oct 2026·absent—
v2.1.30115 Oct 2026·absent—
v2.1.30216 Oct 2026·absent—
v2.1.30318 Oct 2026·absent—
v2.1.30419 Oct 2026·absent—
v2.1.30520 Oct 2026·absent—
v2.1.30621 Oct 2026·absent—
v2.1.30721 Oct 2026·absent—
v2.1.30822 Oct 2026·absent—

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the settings key does. All settings keys.

Feedback