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

Claude Code v2.1.227 ·

Sync work per turn is capped by time, path count, row count and file size

Per-turn syncing is capped by time, path count and a 64 MiB file size limit.

You'll notice New Features
JSON All of v2.1.227
You'll noticeTier: how much it should matter to you
3Useful: 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

The syncer enforces published limits so a turn cannot be delayed indefinitely by file transfer. The pre-turn pull is bounded by WORKER_SYNC_BEFORE_TURN_CAP_MS at 10000 ms, dropping to WORKER_SYNC_DEGRADED_CAP_MS at 500 ms once the connection is degraded. Pushing looks at 4096 candidate paths per turn at most and refuses any file over 64 MiB, so very large files never sync.

Details
  • Surplus paths beyond 4096 rotate across later turns rather than being dropped.
  • At most 40 new entries are admitted per turn against a 256-entry cap, with some of that cap held in reserve.
  • The published record of worker state is capped at 2 MiB, with at most 256 recorded entries and 256 recorded skips.
  • If a previous worker process still holds the sync, the apply step retries up to MAX_APPLY_ATTEMPTS (3) times with APPLY_RESTART_DELAY_MS (5000 ms) between attempts.
Evidence

WORKER_SYNC_BEFORE_TURN_CAP_MS

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