A cloud pull now stashes uncommitted files it overwrites into .claude-cloud-trash and tells you where.
What's wrong with this entry?
When 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.
- The trash directory carries its own
.gitignoreso the copies do not show up as changes. - A
tengu_dir_sync_anchorevent records which storage backend anchored the write. - The older manifest-apply and journal pull paths were removed in the same release.
.claude-cloud-trash
Strings lifted out of the shipped bundle, so the claim above can be checked against them.