{"version":"2.1.283","anchor":"machine-side-sync-files-handler-for-cloud-session-directory","canonical_anchor":"machine-side-sync-files-handler-for-cloud-session-directory","heading":"Your machine now answers file sync requests from its cloud session","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/machine-side-sync-files-handler-for-cloud-session-directory","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Your machine now answers file sync requests from its cloud session\n\nA machine bound to a cloud session now handles its file sync calls, pulling the session's changes in and, when asked, sending the checkout up\n\n**Unclear.** What turns this handler on is not stated.\n\n**What**\n\nThe cloud side could already ask the machine to sync files. Claude Code on the machine now handles those requests. It pulls the session's latest file changes into the local checkout and, when asked, sends the checkout's state up. The session calls this around the commands it runs on the machine; you do not call it yourself. A sync job can be rejoined by its id, and up to 16 jobs are tracked.\n\nCalls are refused when:\n\n- the sender is held back under the trusted-device policy, reported as `unattested_request`\n\n- no sync engine is running\n\n- the folder is not syncing\n\n- too many calls are already running\n\n**Why**\n\nIt completes two-way file sync between a cloud session and the machine it is bound to.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5"}