{"version":"2.1.248","anchor":"plan-files-can-be-watched-through-the-newer-storage-backend","canonical_anchor":"plan-files-can-be-watched-through-the-newer-storage-backend","heading":"Plan files can be watched through the newer storage backend","tier":"soon","area":"Plan Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/plan-files-can-be-watched-through-the-newer-storage-backend","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Plan files can be watched through the newer storage backend\n\nPlan files can stay in sync via change notifications on the newer storage backend.\n\n**What**\n\nPlan files (the saved output of plan mode) can be kept in sync by subscribing to change notifications from Claude Code's newer storage backend instead of re-reading on demand. It only runs when that backend is both selected by an internal check and passed in, so on the older storage path nothing changes.\n\n**Details**\n\n- Per-plan subscription with generation counters, refresh on change events, one automatic resubscribe if the watch ends, release of stale watches, and a cap on how long a read will wait.\n- If subscribing fails it logs and serves the last value read plus any writes made in this process, so a plan is never unavailable.\n- The check that selects the newer backend is compiled down to an unnamed predicate, so which flag or setting decides it is not visible in the build.\n\n**Evidence**\n\n`plans: watching `\n\n- Area: Plan Mode\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}