{"version":"2.1.300","anchor":"cloud-session-teleportremote-checks-handle-missing-sign-in","canonical_anchor":"cloud-session-teleportremote-checks-handle-missing-sign-in","heading":"Cloud session checks now share one message when you are not signed in","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/cloud-session-teleportremote-checks-handle-missing-sign-in","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Cloud session checks now share one message when you are not signed in\n\nSeveral cloud session checks now get your sign-in token a new way and share one error message when you are not signed in\n\n**Unclear.** The wording of the new shared message is not given, so it is unclear whether it still tells you to run `claude auth login`.\n\n**What**\n\nSeveral checks for cloud sessions now get your sign-in token in a different way:\n\n- resuming a cloud session on your own computer, called teleport\n\n- checking that the GitHub app is installed, and checking tokens\n\n- checking whether you can use remote sessions\n\nWhen no token can be obtained, these checks now report that you are not logged in, or they show a shared error message. Before, they used a message built into each check that told you to run `claude auth login`. The check for remote sessions also skips the GitHub app check when you are not signed in.\n\n**Why**\n\nThis changes the path that cloud sessions take when your sign-in is missing, so the error you see in that case may read differently.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}