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.242 Home All releases ←olderv2.1.241 v2.1.243newer→
Claude Code v2.1.242

Cloud session sync for folders that are not git checkouts

Not switched on
Useful3 Signal4
Cloud Sessions Notable not in their notes

Cloud sessions could sync a plain folder, not just a git checkout, if an env var is set.

Folder consent wording is already visible, but the archive engine only builds when CLAUDE_CODE_DIR_SYNC_ARCHIVE is set.

CLAUDE_CODE_DIR_SYNC_ARCHIVE
What

Cloud sessions can now be started from an ordinary directory rather than a git checkout, using a second sync engine that applies file archives sent from your machine, keeps a session-side trash for cloud deletions, and tells the model exactly which files never cross. The consent prompt that asks whether to copy your files into a cloud session already picks its title, body and "without sync" wording depending on whether you are in a git repository or a plain folder, so the folder wording is visible in this build. The folder engine itself is only constructed when the environment variable CLAUDE_CODE_DIR_SYNC_ARCHIVE is set and its enabled check passes, so with that variable unset the prompt wording is present but no folder sync happens.

Details
  • The folder version of the consent prompt spells out what stays behind: anything the top-level .gitignore excludes, dot-named files and directories, and git repositories nested inside the folder.
  • The sync itself excludes dot-files, dependency and build folders, credential-named files, symlinks, editor leftovers, and files over the size limit.
  • Which engine is in play is decided by the archive engine check, and on the worker path by CLAUDE_CODE_DIR_SYNC_ARCHIVE; with the variable unset nothing is constructed and the git-based engine remains the only path.
  • When your copy and the cloud copy of a file conflict, your version is kept under the original name.
  • Sync bookkeeping lives in a .ccr-dir-sync directory at the top of the synced folder.
  • New reasons are recorded internally for why the consent prompt was skipped, and an event named dir_sync_worker_archive_armed marks the folder worker being armed.
Evidence

Allow Claude Code to copy the files in this folder (never ones its top-level .gitignore excludes, dot-named files or directories, or git repositories inside it) into cloud sessions you start here, so a session works on your current files and can keep going while this machine is off. Synced files are encrypted at rest., dir_sync_worker_archive_armed

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.242 →