{"version":"2.1.234","anchor":"global-config-file-watching-can-move-onto-the-storage-backen","canonical_anchor":"global-config-file-watching-can-move-onto-the-storage-backen","heading":"Global config file watching can move onto the storage backend","tier":"internal","area":"Storage Backend","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/global-config-file-watching-can-move-onto-the-storage-backen","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Global config file watching can move onto the storage backend\n\nYour global config can be watched through the storage backend instead of the file, falling back if it fails.\n\n**What**\n\nClaude Code watches `~\/.claude.json` so changes made by another running process are picked up. A new path subscribes to that config through the storage backend instead and stops watching the file once the subscription succeeds; if it fails, the existing file watcher stays in place.\n\n**Details**\n\n- The config state now also records which backend supplies freshness and holds a one-shot claim for resubscribing.\n- Requires both the storage v5 pin (`tengu_hover_rest`, falling back to false) and a constructed backend, and this build cannot construct one, so the file watcher is what actually runs.\n\n**Evidence**\n\n`Watching ~\/.claude.json for other processes through the storage interface`\n\n- Flag `tengu_hover_rest`: Off in both readings (read for one account on one subscription tier against v2.1.234; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Storage Backend\n- Names: `~\/.claude.json`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}