Follow Discord
Sweep 28 Sep 2026 · 17:20Z Build v2.1.284 505 read Stable v2.1.274 Latest v2.1.283 Next v2.1.284 Feeds RSS JSON llms.txt llms-full.txt Unofficial
Writing the changelog v2.1.284 compose entry prose · 2/5

Claude Code v2.1.280 ·

Git-sync now explains more precisely why previously-staged changes were dropped

Git-sync now gives a more specific reason when your earlier staged changes are no longer there

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

When Claude Code's git-sync feature finds that changes it had previously staged are no longer in the index, it now explains more precisely why. The message now distinguishes between three cases:

  • the file is gone entirely
  • the file's contents have changed since, in which case Claude is told to re-read it
  • the contents are unchanged

Previously the message always said the file contents were unchanged, even when that wasn't true.

Why

A more accurate explanation helps Claude respond correctly when its staged work disappears: it knows whether to re-read a changed file before continuing, rather than assuming nothing had changed.

See this entry in the whole of v2.1.280 →

Feedback