{"version":"2.1.281","anchor":"remote-file-sync-status-gains-held-open-turn-end-and-a","canonical_anchor":"remote-file-sync-status-gains-held-open-turn-end-and-a","heading":"Remote file-sync status gains \"held_open\", \"turn_end\" and \"awaiting_container\" explanations","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/remote-file-sync-status-gains-held-open-turn-end-and-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Remote file-sync status gains \"held_open\", \"turn_end\" and \"awaiting_container\" explanations\n\nThree new reasons explain why a remote machine has not received a session's file changes: held_open, turn_end and awaiting_container\n\n**What**\n\nWhen a session's file changes have not yet reached a remote machine, Claude Code gives the model a reason, with a cause and a suggested remedy. The model is the AI that does the work. Three reasons are new:\n\n- `held_open`: the files are open in another program on the remote machine.\n\n- `turn_end`: the remote machine takes in changes when the current turn ends.\n\n- `awaiting_container`: the remote machine could not download an earlier upload. It accepts nothing newer until the session sends its changes in a form it can take.\n\n**Why**\n\nWith a specific reason, Claude can tell you why your edits have not appeared on the other machine and what would fix it, rather than giving a generic \"not synced yet\".\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}