{"version":"2.1.219","anchor":"teleport-branch-mismatch-error-explains-what-the-checkout-ac","canonical_anchor":"teleport-branch-mismatch-error-explains-what-the-checkout-ac","heading":"Teleport branch-mismatch error explains what the checkout actually is","tier":"notice","area":"Teleport","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/teleport-branch-mismatch-error-explains-what-the-checkout-ac","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### Teleport branch-mismatch error explains what the checkout actually is\n\nTeleport now tells you whether the repo genuinely mismatched or the git remote just couldn't be read.\n\n**What**\n\nThe \"You must run claude --teleport ... from a checkout of ...\" error now tells you why the current directory did not match, separating a genuine repo mismatch from a git remote it could not parse.\n\n**Details**\n\n- repo mismatch shows the session's repo plus a \"This repo is ...\" line\n- an unparseable remote reports that case explicitly instead of implying a mismatch\n- the session repo is qualified with its host when the host is not the default\n\n**Evidence**\n\n`Couldn't parse your git remote: `\n\n- Area: Teleport\n- Names: `claude --teleport`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}