Your custom keybindings can load in the background at startup so they're ready sooner.
tengu_keybinding_customization_release Off by default, switched on for this accountThe shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.
This account: on · anonymous baseline: on · compiled default in v2.1.225: off
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
What's wrong with this entry?
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.