The cross-directory sync warning is built but gated on a remote flag that is false when the lookup fails.
On 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.
- The scan is bounded and runs in batches, so it does not walk the whole machine.
- Separately, the sync offer no longer prints "Checking whether this checkout can sync…" to stderr; the decision now happens inside a wrapper that reports skipped cases as
tengu_dir_sync_mode_prompt_skipped.
File sync for this session was set up from another directory on this machine, not
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_violin_wood Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.239: off
Read once, for one account on one subscription tier, against v2.1.239. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.