{"version":"2.1.239","anchor":"cloud-pull-keeps-a-copy-of-uncommitted-files-it-overwrites","canonical_anchor":"cloud-pull-keeps-a-copy-of-uncommitted-files-it-overwrites","heading":"Cloud pull keeps a copy of uncommitted files it overwrites","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/cloud-pull-keeps-a-copy-of-uncommitted-files-it-overwrites","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Cloud pull keeps a copy of uncommitted files it overwrites\n\nA cloud pull now stashes uncommitted files it overwrites into .claude-cloud-trash and tells you where.\n\n**What**\n\nWhen a cloud session's files replace local ones, any file with uncommitted changes is copied into a `.claude-cloud-trash` directory before being overwritten, and you are told where the copies are. If no copy could be kept, the message says so plainly rather than staying quiet.\n\n**Details**\n\n- The trash directory carries its own `.gitignore` so the copies do not show up as changes.\n- A `tengu_dir_sync_anchor` event records which storage backend anchored the write.\n- The older manifest-apply and journal pull paths were removed in the same release.\n\n**Evidence**\n\n`.claude-cloud-trash`\n\n- Area: Cloud Sessions\n- Names: `.claude-cloud-trash`\n- Tier: You'll notice\n- Useful: 5\/5\n- Signal: 3\/5"}