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.227 ·

Sync stops itself after repeated auth refusals, repeated crashes, or a rehomed workspace

Worker syncing shuts itself off after repeated auth failures, crashes or a moved workspace.

You'll notice New Features
JSON All of v2.1.227
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Remote SyncArea: what it touches
New FeaturesKind: in v2.1.227,
New FeaturesSection of the release
What

Rather than retrying forever, the worker syncer turns itself off on three conditions and the session continues without syncing.

Details
  • MAX_CONSECUTIVE_AUTH_REFUSALS (10) consecutive auth refusals, or a single response saying the session is refused, disarms it with a dir_sync_worker_session_refused warning.
  • MAX_CONSECUTIVE_PHASE_CRASHES (3) unexpected exceptions in a pull or push phase also disarms it; each crash logs dir_sync_worker_phase_crashed with the error name, error code and consecutive count.
  • If a resumed worker finds itself pointed at a workspace that already has a non-empty published record from someone else, it logs dir_sync_worker_rehomed_disarmed and stops rather than merging the two.
Evidence

dir_sync_worker_rehomed_disarmed

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.227 →

Feedback