Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Cloud SyncArea: what it touches
Internal ChangesKind: in v2.1.265,
Internal ChangesSection of the release
What
A function that records failed directory-sync notifications (notSent) now takes an option to skip adding the failure to the persistent report log, while still updating the live status line so the current state is visible. The related retry message also now mentions retrying at "the next sync point," in addition to the existing "after every turn" wording.
Why
This lets Claude Code show a sync problem in the moment without necessarily cluttering the persistent report with every occurrence, while still being clear about when a retry will happen.
