tengu_sunny_locket

A Claude Code feature flag, read out of the shipped bundle. It was in the build from v2.1.283 and was gone by v2.1.307.

Releases whose published page names tengu_sunny_locket.

1. v2.1.314 30 Oct 2026
   Idle compaction's one-hour cache handling no longer waits on a remote switch

   One-hour cache idle compaction is now always on in code; keepalive is set by a single remote setting that is off by default

   gate cited by this entry

2. v2.1.307 21 Oct 2026
   Idle compaction can also act on keepalive caches, not only one-hour ones

   Idle compaction now covers two cache types, one-hour and keepalive, each with its own setting, and its notice no longer says "after an hour idle"

   gate cited by this entry

3. v2.1.302 16 Oct 2026
   Idle compaction messages now explain the timing and how to turn it off

   When Claude Code compacts while you are idle, it now says it did so before the prompt cache expired and how to turn this off

   gate cited by this entry

4. v2.1.300 14 Oct 2026
   Idle compaction gains a mode that applies the summary when you return

   A new idle compaction mode can swap in a summary written while you were away, off unless it is switched on remotely

   gate cited by this entry

5. v2.1.290 5 Oct 2026
   Idle compaction can be turned off with a setting and tuned with an environment variable

   A new idleCompaction setting turns off background compaction while you're idle, and CLAUDE_CODE_IDLE_COMPACT_MIN_TOKENS sets its size threshold

   gate cited by this entry

6. v2.1.283 25 Sep 2026
   Idle sessions can be compacted before the prompt cache expires

   A remotely controlled option can compact a long, idle conversation shortly before its one-hour prompt cache runs out

   gate cited by this entry

7. v2.1.283 25 Sep 2026
   Groundwork for compacting a conversation while it sits idle, off by default

   Claude Code can compact an idle conversation before its one-hour cache expires, but this is off unless switched on remotely

   gate cited by this entry, found in this entry's text, named in 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.

No release's published evidence quotes this name. The ledger indexes the Evidence lines of every changelog on this site, so this says nobody here has ever quoted it; it says nothing about how old the name is.

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.