Git-based directory sync for cloud sessions includes a lock so only one window syncs.
The sync engine is fully present but per-directory consent depends on an unresolvable flag.
What's wrong with this entry?
The 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.
- 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".
- Its telemetry events
tengu_dir_sync_git_endedandtengu_dir_sync_git_fast_forwardalready existed in 2.1.247; the code appears as new here only because it moved out of a lazily-loaded module into ordinary scope.
git sync writer lock could not be attempted
Strings lifted out of the shipped bundle, so the claim above can be checked against them.