Plan files can stay in sync via change notifications on the newer storage backend.
Only active when the newer storage backend is selected and passed in.
What's wrong with this entry?
Plan 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.
- 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.
- If subscribing fails it logs and serves the last value read plus any writes made in this process, so a plan is never unavailable.
- 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.
plans: watching
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.219
Plan mode can carry a session workshop document
Both mention plan mode
-
v2.1.221
Plan mode prototype-artifact offer
Both mention plan mode
-
v2.1.235
Very large plans cannot be approved
Both mention plan mode