Follow Discord
Sweep 02 Oct 2026 · 18:55Z Build v2.1.288 509 read Stable v2.1.285 Latest v2.1.287 Next v2.1.288 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.287 ·

Nested memory loaded-file tracking removed, and inner calls change how they read files

loadedNestedMemoryPaths is gone, so compaction and sub-contexts no longer manage it, and inner calls drop some file reading settings

Group of 4 You'll notice Bug Fixes
JSON All of v2.1.287
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
CompactionArea: what it touches
Bug FixesKind: in v2.1.287,
Bug FixesSection of the release

What

Nested memory files are CLAUDE.md files in subfolders that Claude Code loads when Claude works in those folders. Claude Code used to keep a list of which ones it had already loaded. That list, loadedNestedMemoryPaths, is removed:

  • The list and its clean-up step evictNestedMemoryPaths are gone.
  • Compaction, which shortens a long conversation by summarising it, no longer clears the list. It still clears readFileState and the memory selector.
  • The list is no longer passed from a parent to sub-contexts such as subagents (helper Claudes that work on a side task).

Two related changes affect inner calls, which are calls made inside another operation:

  • fileReadingLimits is no longer passed to inner calls.
  • For an inner call with no files read yet, dedupUnchangedReads is turned off, so it no longer gets a short "unchanged" answer for a file it never saw.

Why

This changes when nested CLAUDE.md files are brought back into the conversation after compaction or inside subagents. If Claude seems to miss or repeat instructions from a subfolder's CLAUDE.md after a long session, this is the area that changed.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhether the reset of how memory files are chosen brings those files back into the conversation anyway is not settled.

See this entry in the whole of v2.1.287 →

Feedback