{"version":"2.1.300","anchor":"untracked-files-now-block-teleport-to-cloud","canonical_anchor":"untracked-files-now-block-teleport-to-cloud","heading":"Moving a session to the cloud now stops if the branch has untracked files","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/untracked-files-now-block-teleport-to-cloud","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Moving a session to the cloud now stops if the branch has untracked files\n\nTeleporting a session to the cloud is now refused when the branch has untracked files, with advice to commit and push them or run `git stash -u`\n\n**What**\n\nTeleporting moves your current session into a cloud session, which runs on Anthropic's servers instead of on your computer. Before it starts, Claude Code checks the state of your git branch. It already stopped the move when you had uncommitted changes or commits that were not pushed.\n\nIt now also stops when the branch has untracked files. These are files in your folder that git has never been told to track. The message says the cloud session clones the project from the remote copy, so it won't have those files. It suggests you either commit and push them, or set them aside with `git stash -u`.\n\n**Why**\n\nA cloud handoff that used to go ahead with stray untracked files will now be refused. You have to deal with those files first, which also means the cloud session is not left silently missing them.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}