tengu_smooth_chipmunk

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

Releases whose published page names tengu_smooth_chipmunk.

1. v2.1.282 24 Sep 2026
   Auto mode now falls back to server-side permission checks when no setting is sent

   In auto mode, Claude Code now falls back to Anthropic's server-side classifier for permission decisions when the server sends no value for that setting

   gate cited by this entry, found in this entry's text

2. v2.1.281 23 Sep 2026
   CLAUDE_CODE_AUTO_MODE_SERVER now overrides the server-classifier gate both ways

   Setting CLAUDE_CODE_AUTO_MODE_SERVER now forces server classifier review on or off, whichever way it is set

   gate cited by this entry, found in this entry's text

3. v2.1.281 23 Sep 2026
   Setting CLAUDE_CODE_AUTO_MODE_SERVER now controls the server-side auto-mode classifier for first-party users, not only third-party

   CLAUDE_CODE_AUTO_MODE_SERVER now also switches the server-side auto-mode classifier on or off for first-party connections

   gate cited by this entry, found in this entry's text

4. v2.1.269 11 Sep 2026
   New "arbiter" mode for the server-side auto-mode classifier

   Auto-mode's safety classifier gained a new 'arbiter' mode that can skip some server checks

   gate cited by this entry

5. v2.1.261 4 Sep 2026
   Server-side auto-mode dangerous-tool-use classifier

   Auto mode's dangerous-action classifier now runs server-side and blocks actions it flags or can't reach.

   gate cited by this entry

6. v2.1.261 4 Sep 2026
   Auto-mode permission context payload (git state, chrome nav, trusted dirs) sent for classification

   Auto-mode permission classification now sends a richer context payload including git and Chrome state.

   gate cited by this entry

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.

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.

The earliest release whose published evidence quoted tengu_smooth_chipmunk was v2.1.282, 24 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.

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.

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.