Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.283 ·

Claude is told which memory files a background save just wrote

When background memory saving writes files, the main conversation is told which ones changed so it rereads them instead of using an old copy

You'll notice Improvements
JSON All of v2.1.283
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
MemoryArea: what it touches
ImprovementsKind: in v2.1.283,
ImprovementsSection of the release
What

Claude Code can save memories in the background. A separate pass looks over the conversation and writes notes to memory files on disk. When that pass writes files, it now leaves a notice for the main conversation, summarised as "saved N memories" or "updated the memory index". The memory index is the file that lists your memories.

  • Each file the pass wrote is also refreshed in the main conversation's record of which files it has already read.
  • If the pass fails partway through, the notice is still sent for the files it managed to write before the error.

In the previous build, the background pass left no notice at all.

Why

Claude may already have a memory file loaded from earlier in the conversation. The notice tells it that this copy no longer matches what is on disk and that it should read the file again. That stops Claude from editing a memory file based on an out-of-date copy.

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 doubtIt is not clear whether background memory saving is switched on for every user.

See this entry in the whole of v2.1.283 →

Feedback