A dialog can ask whether to copy your repo, including uncommitted files, into cloud sessions.
A per-repository remoteFileMode sync consent dialog is built behind a flag treated as off on error.
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.227: not a boolean we can read
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.227. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
A new dialog asks whether Claude Code may copy the current repository, including uncommitted and untracked files but never gitignored ones, into cloud sessions started from that directory. The options are "Yes, sync this repository", "No, don't sync" and "Not now", which is focused by default. The answer is saved per repository as remoteFileMode. The prompt is gated on the tengu_violin_wood flag, which is treated as off if it errors.
- Reports
tengu_dir_sync_mode_prompt_shownandtengu_dir_sync_mode_promptwith the chosen value. - Skips are reported as
tengu_dir_sync_mode_prompt_skippedwith reasonnot_attached,no_git_rootoranswered.
Sync this repository to the cloud?
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.224
Untracked files can be seeded into a cloud session
Both mention file mode
-
v2.1.224
Untracked files can be uploaded to a cloud session's working directory
Both mention file mode
-
v2.1.239
File uploads report why they failed and stop retrying forever
Both mention file