{"version":"2.1.283","anchor":"directory-sync-restore-after-a-container-replacement-is-now","canonical_anchor":"directory-sync-restore-after-a-container-replacement-is-now","heading":"Restored cloud work now reflects the last upload, not the end of your last turn","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/directory-sync-restore-after-a-container-replacement-is-now","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Restored cloud work now reflects the last upload, not the end of your last turn\n\nAfter a cloud environment is recreated, restore messages now say files are as of the last upload, and the end-of-last-turn case is gone\n\n**What**\n\nWhen a cloud environment is recreated, directory sync restores Claude's work into the new one. The message for a full restore now says the files are as they stood when the earlier environment last uploaded them, and that anything changed after that upload is missing. It used to say the files were as you left them at the end of your last turn.\n\n- The separate outcome and report for a restore up to your last completed turn were removed.\n\n- A partial restore is now described as reaching one of that environment's earlier uploads.\n\n**Why**\n\nIn practice, work done after the last upload before a container was replaced is not brought back, and the message now says so.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}