Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.246 ·

Sync journal accepts transports it does not recognise

Sync records survive an unfamiliar transport name instead of being thrown out entirely.

Under the hood Internal Changes
JSON All of v2.1.246
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Cloud SyncArea: what it touches
Internal ChangesKind: in v2.1.246,
What probably matters to youSection of the release
What

The field naming how a bundle travelled changed from a fixed choice of two values to any short string, normalised to "row", "direct" or "unknown", with size caps looked up per transport. A newer server transport now passes through an older reader instead of invalidating the whole record.

Details
  • The laptop side refuses to write a journal note whose bundle normalised to "unknown".
  • The same note gained an origin field that only survives the round trip as "folder".
Evidence

sync journal note is not one its reader would accept, or rides with rows

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.246 →

Feedback