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

tengu_peppy_gosling

flag in the build JSON

A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.314, including the newest one read.

In remote sessions with a small context window, a server value can now raise the CLAUDE_AUTOCOMPACT_PCT_OVERRIDE threshold, up to 100

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

First seen v2.1.314 30 Oct 2026
Last seen v2.1.322 10 Nov 2026
Builds8 / 161on this box, as of v2.1.322
Written about v2.1.314 first named in a changelog, 30 Oct 2026
v2.1.314in the build not in the build never minedv2.1.322

In the changelogs

1

Releases whose published page names tengu_peppy_gosling.

  1. v2.1.314
    Remote sessions can have their auto-compaction point raised from the server

    In remote sessions with a small context window, a server value can now raise the CLAUDE_AUTOCOMPACT_PCT_OVERRIDE threshold, up to 100

    gate cited by this entry

Gate readings

1
ReleaseResolvedThis accountAnonymousCompiled default
v2.1.314 read on another version Not enough to say no value returned no value returned not a boolean we can read

Two arms, because they disagree: this account is the one account this site reads and anonymous is a baseline with no identity attached. A reading says nothing about your account, and off cannot rule out a rollout both readings sit outside of. What these readings can and cannot show.

Flag server, over time

2
Read asReadingFromUntilVersion installed
this account null 2026-10-28T23:30:09Z 2026-11-12T07:45:05Z v2.1.312 to v2.1.322
anonymous null 2026-10-28T23:20:06Z 2026-11-12T07:45:05Z v2.1.312 to v2.1.322

One row per unbroken stretch of one reading, newest first, from snapshots taken every twenty-five minutes or so. No longer carried is not off: it means the flag server stopped returning the gate at all, which is what a retired experiment looks like. The version column is what was installed when the reading was taken, not what caused it.

First cited

1

The earliest release whose published evidence quoted tengu_peppy_gosling was v2.1.314, 30 Oct 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.31430 Oct 2026tengu_peppy_gosling

Presence across releases

1
BuildsHow manyDatesReading
v2.1.314 – v2.1.3228 builds30 Oct 2026 → 10 Nov 2026 ◆in the build

Build by build

8

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.31430 Oct 2026·addedverdict: added · default number
v2.1.31530 Oct 2026·presentverdict: present · default number
v2.1.31631 Oct 2026·presentverdict: present · default number
v2.1.3172 Nov 2026·presentverdict: present · default number
v2.1.3183 Nov 2026·presentverdict: present · default number
v2.1.3196 Nov 2026·presentverdict: present · default number
v2.1.3219 Nov 2026·presentverdict: present · default number
v2.1.32210 Nov 2026·presentverdict: present · default number

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

Feedback