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.
What
Several checks for cloud sessions now get your sign-in token in a different way:
- resuming a cloud session on your own computer, called teleport
- checking that the GitHub app is installed, and checking tokens
- checking whether you can use remote sessions
When 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.
Why
This changes the path that cloud sessions take when your sign-in is missing, so the error you see in that case may read differently.
claude auth login
Claude Code changelog modified, high confidence
- Improved the error shown when a cloud session is refused because your claude.ai login was rejected or has expired: it now tells you to sign in again with `claude auth login`see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The wording of the new shared message is not given, so it is unclear whether it still tells you to run `claude auth login`.
Anthropic's documentation agrees
claude auth login on Claude Code changelog