What
When CLAUDE_CODE_DIR_SYNC_ENGINE is set to none, off, 0, false or no, resuming a git or folder session attaches a visibly stopped sync engine and explains the situation in words instead of silently doing nothing. Before this, the git path just returned with no engine and no message. Sync is treated as on unless that variable holds one of those values.
Details
- The stopped engine reports the line "sync is switched off on this machine" and carries
reason: "engine_declined", with the decline recorded in telemetry asattach_engine_declined. - The full explanation reads "File sync is switched off on this machine by CLAUDE_CODE_DIR_SYNC_ENGINE, so this session does not sync here now; unset it and open the session again to resume."
- A companion message warns that the cloud copy will be emptied so the local and remote sides do not drift apart.
- A shared phrasing helper generates the wording for each of the reasons sync can stop, so the messages stay consistent across cases.
- Attachment now checks whether the engine is permitted before doing any other setup work.
- Resumed folder and git records also carry
endedEarlierwhen the stored record shows a previous run ended.
Evidence
y("ccr_dir_sync_pull", "attach_engine_declined"), attach_engine_declined, File sync is switched off on this machine by CLAUDE_CODE_DIR_SYNC_ENGINE, so this session does not sync here now; unset it and open the session again to resume.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundleCLAUDE_CODE_DIR_SYNC_ENGINE