Follow Discord
Sweep 30 Oct 2026 · 01:02Z Build v2.1.314 532 read Stable v2.1.308 Latest v2.1.314 Next v2.1.314 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.314 ·

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

Under the hood Internal Changes
JSON All of v2.1.314
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
CompactionArea: what it touches
Internal ChangesKind: in v2.1.314,
Internal ChangesSection of the release
What

Idle compaction is when Claude Code replaces older messages with a shorter summary while you are away. The two kinds of prompt cache it handles are now controlled differently:

  • The one-hour cache no longer has its own remote switch. It is always on in the code.
  • The keepalive cache is controlled by one remote setting with a mode. "compact" turns it on, "log" only records what would happen, and anything else turns it off. With nothing sent from the server it is off.

A minimum conversation size, read from CLAUDE_CODE_IDLE_COMPACT_MIN_TOKENS, also applies. Tokens are the small pieces of text a model counts.

Why

Idle compaction is now rolled out differently. The one-hour cache part no longer depends on anything being switched on remotely, while the keepalive part stays off unless it is switched on remotely.

Read from
Feature flag
tengu_bubbly_canyon Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.314: not a boolean we can read

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

tengu_sunny_locket Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.314: not a boolean we can read

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.314. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns {"mode":"compact"} for tengu_sunny_locket, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns {"mode":"off"} for tengu_sunny_locket, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns {"mode":"compact"} for tengu_sunny_locket, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns {"mode":"off"} for tengu_sunny_locket, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns {"mode":"compact"} for tengu_sunny_locket, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns {"mode":"off"} for tengu_sunny_locket, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns {"mode":"compact"} for tengu_sunny_locket, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns {"mode":"off"} for tengu_sunny_locket, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_bubbly_canyon

See this entry in the whole of v2.1.314 →

Feedback