{"version":"2.1.281","anchor":"remote-tool-guidance-on-file-sync-timing-rewritten-cloud-se","canonical_anchor":"remote-tool-guidance-on-file-sync-timing-rewritten-cloud-se","heading":"Remote-tool guidance on file sync timing rewritten (cloud sessions)","tier":"notice","area":"Remote Devices","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/remote-tool-guidance-on-file-sync-timing-rewritten-cloud-se","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Remote-tool guidance on file sync timing rewritten (cloud sessions)\n\nInstructions telling Claude when remote file sync output arrives were reworded, and a sentence about being told when sync cannot happen was removed\n\n**What**\n\nIn some cloud sessions a remote machine is kept in sync with the session. Claude receives written instructions about when files and output travel between the two. That text has changed:\n\n- Output from a remote call is now described as \"usually\" sent back and taken in \"between your tool calls once it has landed\". A tool call is one action Claude takes, such as running a command.\n\n- Claude is told that reading new output on the remote machine may take \"possibly for the whole turn\".\n\n- The sentence saying that, if the machine cannot send it now, Claude is told so and what to expect, was removed from the default and after-task versions of the text.\n\n**Why**\n\nThese are instructions to Claude, not messages shown to you. They set looser expectations about when remote output shows up, so Claude may wait longer before it sees results from a remote machine.\n\n- Area: Remote Devices\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}