Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.248 Home All releases ←olderv2.1.247 v2.1.250newer→
Claude Code v2.1.248

Plan file cache stays coherent across resume, fork and recovery

You'll notice
Useful3 Signal2
Plan Mode

Resume, fork and recovery keep the plan file cache warm instead of racing to rebuild it.

What

Resume, fork and recovery paths now write the content they just produced back into the plan file cache rather than invalidating it, via new settle, observe and watch helpers, and resume priming is tracked as a single in-flight promise so concurrent callers wait on one pass instead of racing.

Details
  • Sits behind the same in-module condition that already guarded the plan file cache; what that condition reads is not visible from the cache code itself.
Evidence

settlePlanFile

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.

See this entry in the whole of v2.1.248 →