{"version":"2.1.248","anchor":"git-based-file-sync-for-cloud-sessions-with-a-takeover-lock","canonical_anchor":"git-based-file-sync-for-cloud-sessions-with-a-takeover-lock","heading":"Git-based file sync for cloud sessions, with a takeover lock","tier":"soon","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/git-based-file-sync-for-cloud-sessions-with-a-takeover-lock","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Git-based file sync for cloud sessions, with a takeover lock\n\nGit-based directory sync for cloud sessions includes a lock so only one window syncs.\n\n**What**\n\nThe engine that syncs a directory to a cloud session over git is fully present here, including a writer lock so only one window syncs at a time. The losing window shows \"Another Claude Code window took over syncing this session; this one stopped\". Whether sync runs at all for a directory depends on a per-directory consent read that can come back unknown, in which case you see that the setting could not be read because the feature flag did not answer; the flag's name is not resolvable from the build.\n\n**Details**\n\n- Also covers upload retry ladders, fast-forwarding the sync branch, and status lines such as the give-up message and \"File sync ended earlier in this session\".\n- Its telemetry events `tengu_dir_sync_git_ended` and `tengu_dir_sync_git_fast_forward` already existed in 2.1.247; the code appears as new here only because it moved out of a lazily-loaded module into ordinary scope.\n\n**Evidence**\n\n`git sync writer lock could not be attempted`\n\n- Area: Cloud Sessions\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}