The tengu_hidden_frog setting now controls whether reactive compaction can fall back, instead of an old auto-enable check that is now permanently off
What
An internal setting called tengu_hidden_frog used to control whether Claude Code would automatically enable a certain feature and reset related state. That old check has been hardwired off, so it no longer does anything.
The same setting is now read in a new spot, with its default flipped from off to on, where it decides whether "reactive compaction" (a process that trims conversation history to save space) is allowed to fall back to an alternate method when needed.
Why
This moves what the setting controls from a now-disabled auto-enable path to a live fallback decision for reactive compaction, so the setting still matters but for a different purpose than before.
tengu_hidden_frog On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.269: on
Read once, for one account on one subscription tier, against v2.1.269. It isn't a statement about your account. What a flag value here can and cannot tell you