Startup, after prefetch, can run an async warm read that populates keybindings from the storage backend ahead of first use, tracked by a warmedFromBackend flag.
- the warm read suppresses feature events; the next synchronous read re-validates and discards the warmed value if customization is disabled, so a backend-loaded set does not survive the feature being turned off
- warming is skipped in non-interactive mode and when the feature is off
- a backend read failure during warming logs the telemetry reason
warm_backend_read_failed_fell_back - hot-reload and delete paths clear the flag
- gated on
tengu_keybinding_customization_release, which falls back to true
warm_backend_read_failed_fell_back, warmedFromBackend
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_keybinding_customization_release 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.225: on
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.225. It isn't a statement about your account. What a flag value here can and cannot tell you
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.
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.