Follow Discord
Sweep 28 Sep 2026 · 18:16Z Build v2.1.284 505 read Stable v2.1.277 Latest v2.1.284 Next v2.1.284 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.284 ·

Remote directory sync now snapshots after every 5 writing tool calls

In remote containers, directory-sync snapshots now fire after 5 writing tool calls instead of following quiet-time and max-wait timers

Group of 2 You'll notice Improvements
JSON All of v2.1.284
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
ImprovementsKind: in v2.1.284,
ImprovementsSection of the release

What

When Claude works in a remote container, the working folder is synced back to your side using snapshots, which are copies of the folder at one moment. The rule for when a snapshot is taken has changed:

  • A snapshot is due once 5 writing tool calls of unknown kind have built up. A tool call is one action Claude takes, such as running a command.
  • Snapshots stop after 3 consecutive failures.
  • The count resets after each snapshot finishes.
  • Snapshots that were cancelled are ignored, and snapshots that found nothing changed no longer count as failures.
  • The old timing is gone: idleStrikes, lastAttemptAt, dirtySince, lastHintKind, the minimum gap between attempts and the quietMs/maxWaitMs timers.

The gates named tengu_dir_sync_stream_ship and tengu_dir_sync_snapshot_read_abandoned are involved. Nothing has been read about either.

Why

This changes how often, and when, file changes made in a remote session appear on your side. Updates now follow how much Claude has written rather than how long things have been quiet.

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 doubtWhich sessions use this folder sync, and what turns it on, is not known.

See this entry in the whole of v2.1.284 →

Feedback