You can set CLAUDE_CODE_DIR_SYNC_GIT to pick a git-based engine for syncing your directory to a cloud session.
What's wrong with this entry?
Setting this environment variable now decides which engine syncs your directory to a cloud session worker, and the worker logs that the switch is on when it takes effect. Without it, the previous engine selection applies unchanged.
- The engine actually chosen, and the reason when it ends up as none, are both reported in cloud-session telemetry.
dir_sync_worker_git_switch_on
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.238
Sync state machine gains a moved-root case and a per-turn pull hook
Both mention directory
-
v2.1.238
Untracked-file survey extracted and shared
Both mention directory
-
v2.1.238
Sync internals reshaped around per-file credential state
Both mention directory