{"version":"2.1.239","anchor":"warning-when-a-session-s-file-sync-was-set-up-from-a-differe","canonical_anchor":"warning-when-a-session-s-file-sync-was-set-up-from-a-differe","heading":"Warning when a session's file sync was set up from a different directory","tier":"soon","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/warning-when-a-session-s-file-sync-was-set-up-from-a-differe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Warning when a session's file sync was set up from a different directory\n\nClaude can warn you that a session's file sync was set up elsewhere, but only if the remote gate is on.\n\n**What**\n\nOn attaching to a session, Claude scans other project directories on the machine for the folder this session syncs from, and if it finds one elsewhere it tells you that sync was set up from another directory so edits made here are not uploaded. Gated on `tengu_violin_wood`, which is false when the lookup fails.\n\n**Details**\n\n- The scan is bounded and runs in batches, so it does not walk the whole machine.\n- Separately, the sync offer no longer prints \"Checking whether this checkout can sync\u2026\" to stderr; the decision now happens inside a wrapper that reports skipped cases as `tengu_dir_sync_mode_prompt_skipped`.\n\n**Evidence**\n\n`File sync for this session was set up from another directory on this machine, not `\n\n- Flag `tengu_violin_wood`: Off in both readings (read for one account on one subscription tier against v2.1.239; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Directory Sync\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}