{"version":"2.1.284","anchor":"directory-sync-snapshots-now-fire-after-5-writing-tool-calls","canonical_anchor":"directory-sync-snapshots-now-fire-after-5-writing-tool-calls","heading":"Remote directory sync now snapshots after every 5 writing tool calls","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/directory-sync-snapshots-now-fire-after-5-writing-tool-calls","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Remote directory sync now snapshots after every 5 writing tool calls\n\nIn remote containers, directory-sync snapshots now fire after 5 writing tool calls instead of following quiet-time and max-wait timers\n\n**Unclear.** Which sessions use this folder sync, and what turns it on, is not known.\n\n**What**\n\nWhen 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:\n\n- 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.\n\n- Snapshots stop after 3 consecutive failures.\n\n- The count resets after each snapshot finishes.\n\n- Snapshots that were cancelled are ignored, and snapshots that found nothing changed no longer count as failures.\n\n- The old timing is gone: `idleStrikes`, `lastAttemptAt`, `dirtySince`, `lastHintKind`, the minimum gap between attempts and the `quietMs`\/`maxWaitMs` timers.\n\nThe gates named `tengu_dir_sync_stream_ship` and `tengu_dir_sync_snapshot_read_abandoned` are involved. Nothing has been read about either.\n\n**Why**\n\nThis 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.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}