Unclear The setting that controls this sync was not traced, so who gets this behaviour is unclear.
What
When --cloud runs a session in the cloud, Claude Code can sync a folder and later restore an earlier state of it. This changed in three ways:
- Restoring a target that has no base to rebuild from now stops with a "no basis" result.
- When the store is full, the turn's work stays in the cloud and is marked as not sent back.
- A restore is now either full or partial. The separate "last turn" kind is gone.
Why
If a cloud session's store fills up, some work may stay in the cloud rather than reach your folder.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The setting that controls this sync was not traced, so who gets this behaviour is unclear.