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.227 Home All releases ←olderv2.1.226 v2.1.228newer→
Claude Code v2.1.227

Remote worker sessions now sync the working directory both ways around every turn

Use it now
Useful4 Signal4
Remote Sync Notable not in their notes

Remote worker sessions now sync your working directory both ways around every turn.

CLAUDE_CODE_REMOTE_SESSION_IDCLAUDE_CODE_DISABLE_WORKING_SYNCCLAUDE_CODE_ENVIRONMENT_KIND
What

A remote worker session now pulls files changed on your laptop before each turn and pushes files it changed back after each turn, instead of the previous one-shot copy at startup. It runs only when the session has an SDK URL, CLAUDE_CODE_REMOTE_SESSION_ID is set, and both CLAUDE_CODE_ENVIRONMENT_KIND and CLAUDE_CODE_DISABLE_WORKING_SYNC are unset.

Details
  • The old startup-only entry point startDirSyncApply is gone; the module now exports startWorkerDirSync, which still arms that apply step and then adds beforeTurn (pull and apply incoming files) and afterTurn (push locally changed files, republish the record of what the worker holds).
  • The module is loaded on demand; if the import fails the session logs dir_sync_worker_import_failed and simply runs with no syncing.
Evidence

startWorkerDirSync

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