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

proactivityLevel

setting gone JSON

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

Relaunching Claude Code keeps your proactivity level and permission context instead of resetting them.

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

First seen v2.1.315 30 Oct 2026
Last seen v2.1.316 31 Oct 2026, gone by v2.1.317
Builds2 / 161on this box, as of v2.1.322
Written about v2.1.232 first named in a changelog, 13 Aug 2026
v2.1.315in the build not in the build never minedv2.1.322

In the changelogs

10

Releases whose published page names proactivityLevel.

  1. v2.1.259
    New --proactivity CLI flag (scaffolding only)

    A --proactivity flag is accepted and threaded through session creation, but its value is discarded before it has any effect.

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

  2. v2.1.259
    proactivityLevel plumbed through session/task creation

    A proactivityLevel field now flows through session creation, agent launch, config parsing and telemetry, with no UI or semantics yet.

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

  3. v2.1.259
    Background-forked sessions now inherit proactivityLevel

    Backgrounding a session now carries the parent conversation's proactivity setting into the forked session.

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

  4. v2.1.259
    New proactivityLevel parameter threaded into remote/teleport session creation

    Remote session creation events accept a proactivityLevel field alongside permissionMode, ultraplan, title and thinking.

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

  5. v2.1.239
    How proactive the session is set to be now feeds permission decisions

    Permission and model routing decisions now also see how proactive the session is set to be.

    found in this entry's text

  6. v2.1.233
    API telemetry records the proactivity level

    Query and result telemetry now carry a proactivity level field from your session.

    found in this entry's text

  7. v2.1.233
    Startup telemetry records proactivity level and screen-reader mode

    Startup telemetry now records proactivity level and whether screen-reader mode is on.

    found in this entry's text

  8. v2.1.233
    Proactivity level wired into API request telemetry but never set

    Request telemetry has a slot for a proactivity level, but it is always empty.

    found in this entry's text

  9. v2.1.232
    Proactivity level is carried across a restart

    Relaunching Claude Code keeps your proactivity level and permission context instead of resetting them.

    found in this entry's text

  10. v2.1.232
    A proactivity level is threaded through sessions but does nothing yet

    A proactivityLevel setting is passed around sessions but changes nothing about Claude's behaviour yet.

    found in this entry's text

First cited

9

The earliest release whose published evidence quoted proactivityLevel was v2.1.232, 13 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.23213 Aug 2026proactivityLevel
v2.1.23213 Aug 2026proactivityLevel: t.getProactivityLevel(),
v2.1.23314 Aug 2026proactivityLevel: Eo(b),
v2.1.23314 Aug 2026proactivityLevel: Eo(i),
v2.1.23921 Aug 2026proactivityLevel: u.proactivityLevel
v2.1.2592 Sep 2026proactivityLevel: $1

3 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.315 – v2.1.3162 builds30 Oct 2026 → 31 Oct 2026 ◆in the build
v2.1.317 – v2.1.3225 builds2 Nov 2026 → 10 Nov 2026 ○not in the build

Build by build

7

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.31530 Oct 2026·addedverdict: added
v2.1.31631 Oct 2026·presentverdict: present
v2.1.3172 Nov 2026·removedverdict: removed
v2.1.3183 Nov 2026·absent—
v2.1.3196 Nov 2026·absent—
v2.1.3219 Nov 2026·absent—
v2.1.32210 Nov 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