Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial
Home / Reference / Settings keys

controlOnly

setting never mined JSON

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

Session event stream connections can now request a control-only mode that skips the full event feed

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

First seen — never in a mined build
Last seen — never in a mined build
Builds0 / 161on this box, as of v2.1.322
Written about v2.1.265 first named in a changelog, 8 Sep 2026

In the changelogs

5

Releases whose published page names controlOnly.

  1. v2.1.281
    RemoteSessionManager: serve-only clients and a modeStamp field

    Remote clients set to controlOnly now leave requests they do not support unanswered, and served channel requests carry a modeStamp field

    found in this entry's text

  2. v2.1.265
    Session event stream can connect in control-only mode

    Session event stream connections can now request a control-only mode that skips the full event feed

    found in this entry's text

  3. v2.1.265
    Cloud session 'opened' payload can carry a controlOnly flag

    Cloud session 'opened' event can now carry a controlOnly flag

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

  4. v2.1.265
    Session/control channel gains a 'controlOnly' mode

    Sessions can now run in a 'controlOnly' mode that skips arming the send watchdog

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

  5. v2.1.265
    Session controlOnly flag added to session-open options

    Sessions can now be opened with a controlOnly flag, off by default

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

First cited

6

The earliest release whose published evidence quoted controlOnly was v2.1.265, 8 Sep 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.2658 Sep 2026...(v && { controlOnly: !0 }),
v2.1.2658 Sep 2026controlOnly: e.controlOnly === !0
v2.1.2658 Sep 2026controlOnly: this.config.controlOnly === !0
v2.1.2658 Sep 2026if (this.controlOnly) e.searchParams.set("control_only", "1");
v2.1.28022 Sep 2026onWorkerLive: () => { if (e.controlOnly === !0 && h) F.requestAnnounce("reconnected");
v2.1.28123 Sep 2026writesStatusBeforeInit: e.controlOnly === !0,

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 settings key does. All settings keys.

Feedback