{"version":"2.1.315","anchor":"remote-control-and-file-dial-paths-new-fields-and-waits","canonical_anchor":"remote-control-and-file-dial-paths-new-fields-and-waits","heading":"Small reliability changes for remote and cloud sessions","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/remote-control-and-file-dial-paths-new-fields-and-waits","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Small reliability changes for remote and cloud sessions\n\nRemote sessions get several small changes, including an extra connection check and a sturdier way to spot a failed move to the cloud\n\n**What**\n\nSeveral small changes affect remote sessions, meaning sessions controlled from somewhere other than the computer running Claude Code:\n\n- The client used for remote work gains two new internal fields\n\n- Two steps that deal with sending files now wait for a connection check before running\n\n- When the server refuses access (an HTTP 403 response) and Claude Code refreshes its sign-in token, it now passes an extra flag\n\n- When moving a session to the cloud fails because it is not the right kind of session, Claude Code now recognises this from an error code instead of matching the wording of the message\n\n**Why**\n\nThese make remote sessions less fragile. Recognising an error by its code keeps working even if the error's wording changes.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}