{"version":"2.1.268","anchor":"teleport-failure-message-now-suggests-web-setup-and-points","canonical_anchor":"teleport-failure-message-now-suggests-web-setup-and-points","heading":"Teleport failure message now suggests \/web-setup and points users to retry","tier":"notice","area":"Teleport","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/teleport-failure-message-now-suggests-web-setup-and-points","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Teleport failure message now suggests \/web-setup and points users to retry\n\nTeleport failure messages now suggest running \/web-setup to reuse your GitHub login, then retrying\n\n**What**\n\nWhen a teleport to the cloud fails or is blocked on a precondition, the error message now suggests running `\/web-setup` (which connects your GitHub account using your local `gh` CLI login) to reuse your existing GitHub CLI login, then tells you to rerun `\/teleport` (which pulls a Claude Code on the web session into your terminal).\n\n**Why**\n\nThis turns a teleport failure into an actionable message, giving you a concrete next step to fix a missing GitHub connection instead of just reporting that it failed.\n\n- Area: Teleport\n- Names: `\/web-setup`, `\/teleport`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}