{"version":"2.1.323","anchor":"teleportresume-now-fails-with-a-clear-message-and-uses-sour","canonical_anchor":"teleportresume-now-fails-with-a-clear-message-and-uses-sour","heading":"Bringing a cloud session to your machine fails with a clearer message","tier":"notice","area":"Teleport","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/teleportresume-now-fails-with-a-clear-message-and-uses-sour","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Bringing a cloud session to your machine fails with a clearer message\n\nTeleport now loads only the session's own history, shows a clear error when it is missing, and checks the repository before stashing\n\n**Unclear.** Whether the repository check before stashing is always active or behind a switch is not clear.\n\n**What**\n\nTeleport brings a session that ran in the cloud into your local Claude Code. It changed in these ways:\n\n- It no longer falls back to an older way of loading the session when the main one returns nothing\n\n- It loads only the session's own history, and when that is missing it stops with \"Couldn't load the history of cloud session\"\n\n- It no longer shows a separate \"not found. Run \/status\" message\n\n- Before stashing your local changes, it checks that the folder's `.git` directory still matches the repository the session is tied to, and stashes nothing if it does not\n\nStashing is git's way of setting your uncommitted changes aside.\n\n**Why**\n\nWhen resuming a cloud session goes wrong, you get a plain explanation, and your local changes are not stashed into the wrong repository.\n\n- Area: Teleport\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}