{"version":"2.1.281","anchor":"directory-sync-tells-claude-when-the-sync-service-is-refusin","canonical_anchor":"directory-sync-tells-claude-when-the-sync-service-is-refusin","heading":"Directory sync tells Claude when the sync service is refusing the session","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/directory-sync-tells-claude-when-the-sync-service-is-refusin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Directory sync tells Claude when the sync service is refusing the session\n\nWhen the cloud sync service refuses access, Claude is told once that your latest local changes may not be arriving\n\n**What**\n\nWhen Claude Code runs in the cloud, a background worker copies changes from your own machine's project folder across to the cloud copy (directory sync). If that worker's read is refused as unauthorized, or because the sync channel is unavailable, it now sends Claude a one-time note. The note says newer changes from your machine may not be arriving and that this turn works from the files already there. It also records an event named `tengu_dir_sync_git_worker_lane_refusing`.\n\nIf the sync channel has worked earlier in the session, these refusals no longer make the worker stop for good.\n\n**Why**\n\nClaude is no longer left assuming it sees your newest edits when sync has quietly stopped delivering them, and a temporary refusal no longer shuts down sync for the rest of the session.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}