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
Home / Reference / CLI flags

--messaging-socket-path

cli never mined JSON

A Claude Code CLI flag, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.

The messaging socket lives under XDG_RUNTIME_DIR with locked-down permissions and refuses to hijack a live one.

Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.224.

First seen — never in a mined build
Last seen — never in a mined build
Builds0 / 149on this box, as of v2.1.308
Written about v2.1.224 first named in a changelog, 7 Aug 2026

In the changelogs

6

Releases whose published page names --messaging-socket-path.

  1. v2.1.290
    Messaging between sessions does not start in restricted sessions

    Messaging between sessions no longer starts in a restricted session, or when an explicit messaging socket path is given

    found in this entry's text

  2. v2.1.251
    --messaging-socket-path is now validated and fails startup instead of degrading

    A bad --messaging-socket-path now fails startup instead of leaving your inbox quietly broken.

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

  3. v2.1.248
    Clearer refusals when the socket directory is unsafe, plus container uid detection

    Unsafe socket directories now name the owner, group and mode, and containers are detected.

    found in this entry's text

  4. v2.1.247
    --messaging-socket-path now errors instead of silently doing nothing

    A bad messaging socket path now fails with a clear error instead of being silently ignored.

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

  5. v2.1.232
    Clearer failures when the messaging socket path is unusable

    Messaging socket setup now creates and locks down its directory and explains custom-path failures.

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

  6. v2.1.224
    Local messaging socket: where it lives, who can read it, and refusing to steal a live one

    The messaging socket lives under XDG_RUNTIME_DIR with locked-down permissions and refuses to hijack a live one.

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

First cited

4

The earliest release whose published evidence quoted --messaging-socket-path 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 2026--messaging-socket-path points to a live socket:
v2.1.23213 Aug 2026Choose a different --messaging-socket-path whose directory you own and can make private (0700).
v2.1.24827 Aug 2026start it with a uid map (e.g. unshare -Ur), or pass --messaging-socket-path
v2.1.25128 Aug 2026--messaging-socket-path directory must be a real directory, not a symlink

Presence across releases

0

The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.

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 CLI flag does. All CLI flags.

Feedback