Follow Discord
Sweep 09 Oct 2026 · 17:27Z Build v2.1.296 517 read Stable v2.1.287 Latest v2.1.296 Next v2.1.296 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.296 ·

Transcript syncing no longer re-uploads everything after a failed read

When Claude Code cannot read what the server already holds for a session, it now uploads nothing and retries instead of uploading everything again

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

Claude Code can keep a copy of a session's transcript, the record of the conversation, on the server. To fill in missing parts, it first reads what the server already has. That step changed:

  • A failed read is no longer treated as an empty server. Nothing is uploaded, including the transcripts of subagents (helper agents Claude Code starts), and the log shows [persistence-sync] Main server read failed: nothing uploaded, subagents included.
  • The read is limited to the current session.
  • Only the last compaction record is uploaded as the compaction marker. Compaction is when Claude Code summarizes older conversation to save space.
  • A new retry loop waits longer between attempts and records whether it caught up at once, after a retry, late, or gave up.
Why

Before, a failed read made the whole transcript look missing, so everything was uploaded again, which could leave duplicate or lost entries. Claude Code now holds back and retries instead.

See this entry in the whole of v2.1.296 →

Feedback