Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.248 Home All releases ←olderv2.1.247 v2.1.250newer→
Claude Code v2.1.248

Sessions resumed with directory sync disabled now say so

Use it now
Useful3 Signal3
File Sync Notable not in their notes

Resuming with directory sync turned off now says so instead of quietly doing nothing.

CLAUDE_CODE_DIR_SYNC_ENGINE
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 as attach_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 endedEarlier when 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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.248 →