{"version":"2.1.225","anchor":"keybindings-can-be-pre-warmed-from-the-storage-backend","canonical_anchor":"keybindings-can-be-pre-warmed-from-the-storage-backend","heading":"Keybindings can be pre-warmed from the storage backend","tier":"notice","area":"Terminal UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/keybindings-can-be-pre-warmed-from-the-storage-backend","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Keybindings can be pre-warmed from the storage backend\n\nYour custom keybindings can load in the background at startup so they're ready sooner.\n\n**What**\n\nStartup, after prefetch, can run an async warm read that populates keybindings from the storage backend ahead of first use, tracked by a `warmedFromBackend` flag.\n\n**Details**\n\n- 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\n- warming is skipped in non-interactive mode and when the feature is off\n- a backend read failure during warming logs the telemetry reason `warm_backend_read_failed_fell_back`\n- hot-reload and delete paths clear the flag\n- gated on `tengu_keybinding_customization_release`, which falls back to true\n\n**Evidence**\n\n`warm_backend_read_failed_fell_back`, `warmedFromBackend`\n\n- Flag `tengu_keybinding_customization_release`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.225; this account: on, anonymous baseline: on, compiled default: 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.\n- Area: Terminal UI\n- Names: `tengu_keybinding_customization_release`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}