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 ·

Fewer false "file changed" edit failures after formatters and memory writes

After a hook or the background memory pass rewrites a file, Claude Code updates its record of that file, so a later edit no longer fails as stale

You'll notice Bug Fixes
JSON All of v2.1.283
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
File EditingArea: what it touches
Bug FixesKind: in v2.1.283,
Bug FixesSection of the release
What

Claude Code keeps a record of which files it has read and what they contained. It uses that record to refuse an edit when the file seems to have changed since it was last read. That is a "stale" failure.

A hook is a command you configure to run automatically at a set point. A PostToolUse hook runs after a tool call succeeds, and a tool call is one action Claude takes, such as editing a file. When a PostToolUse hook such as a formatter rewrites a file, Claude Code updates its record to match. This update now covers two more cases:

  • Files Claude had read only partly, when that partial read started at line 1 and had no line limit. Before, any partial read skipped the update.
  • Files written by the background memory pass, the step where Claude Code saves notes to its memory files. Before, these were not updated at all.
Why

In both cases, Claude's next edit to the file could fail because the file looked changed, even though the only change came from a formatter or from Claude Code's own memory writing. You should see fewer of these failed edits.

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 how often the background memory pass runs or what switches it on.

See this entry in the whole of v2.1.283 →

Feedback