{"version":"2.1.290","anchor":"cloud-session-start-notices-explain-what-is-not-copied","canonical_anchor":"cloud-session-start-notices-explain-what-is-not-copied","heading":"Cloud sessions now explain what local work was not copied in","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/cloud-session-start-notices-explain-what-is-not-copied","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Cloud sessions now explain what local work was not copied in\n\nStarting a cloud session now explains when it starts empty or when local commits and uncommitted changes were left out\n\n**Unclear.** It is not clear exactly when each message is shown.\n\n**What**\n\nA cloud session is a Claude Code session that runs on a remote machine instead of your own computer. Claude Code now explains why a cloud session starts empty, meaning nothing from your folder is copied into it. It gives one of these reasons:\n\n- the folder is not a git repository\n\n- you have not confirmed that you trust the folder\n\n- no GitHub repository was found for it\n\nIt also warns when your branch is a number of commits ahead of the remote copy. Those commits, and any uncommitted changes, are not included in the cloud session.\n\n**Why**\n\nIf your local work does not appear in the cloud session, the message tells you why.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}