{"version":"2.1.227","anchor":"remote-worker-sessions-now-sync-the-working-directory-both-w","canonical_anchor":"remote-worker-sessions-now-sync-the-working-directory-both-w","heading":"Remote worker sessions now sync the working directory both ways around every turn","tier":"use","area":"Remote Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/remote-worker-sessions-now-sync-the-working-directory-both-w","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Remote worker sessions now sync the working directory both ways around every turn\n\nRemote worker sessions now sync your working directory both ways around every turn.\n\n**What**\n\nA 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.\n\n**Details**\n\n- 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).\n- The module is loaded on demand; if the import fails the session logs `dir_sync_worker_import_failed` and simply runs with no syncing.\n\n**Evidence**\n\n`startWorkerDirSync`\n\n- Area: Remote Sync\n- Names: `CLAUDE_CODE_REMOTE_SESSION_ID`, `CLAUDE_CODE_DISABLE_WORKING_SYNC`, `CLAUDE_CODE_ENVIRONMENT_KIND`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 4\/5"}