Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.277 ·

Cloud file sync gains a lightweight 'standing' status message

The cloud/local file-sync protocol has a new lightweight 'standing' status distinct from a full sync report

Group of 2 Under the hood Internal Changes
JSON All of v2.1.277
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Directory SyncArea: what it touches
Internal ChangesKind: in v2.1.277,
Internal ChangesSection of the release

Unclear What condition produces the peer_standing outcome and what Claude Code does differently for it is not stated.

What

The git-based cloud/local file-sync protocol gained a new, lightweight journal message kind called standing, decoded by a new function separate from the full worker note/report. When a standing message is present, the client updates its local record from it and returns a new outcome code, peer_standing, instead of the usual outcomes like nothing_new or applied. This new peer_standing value was also added to the retry-outcome switch and related status enum, alongside existing states such as no_journal, yielded, upload_only, and refused.

Why

This gives the sync protocol a cheap way to report a peer's status without sending a full sync report, which should make routine status checks lighter weight.

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 doubtWhat condition produces the peer_standing outcome and what Claude Code does differently for it is not stated.

See this entry in the whole of v2.1.277 →

Feedback