You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
AuthArea: what it touches
ImprovementsKind: in v2.1.304,
ImprovementsSection of the release
What
When claude auth login uses a refresh token from CLAUDE_CODE_OAUTH_REFRESH_TOKEN, it now fetches your account profile before saving the login. It records your subscription type and your rate-limit tier along with it. Before, only the token's permissions were saved. If a restore step fails during this login, a message is now printed.
Separately, the background refresh of managed settings (settings your administrator controls) now tells a check of the managed folder apart from a normal policy refresh.
Why
Machines signed in with a refresh token, such as automated setups, now know the right plan and limits from the start.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed sinceAnthropic's documentation has since written up claude auth login, on Error reference.Each of these messages from `/login`, `claude auth login`, or `claude setup-token` means Claude Code couldn't open the port on `127.0.0.1` where your browser returns the sign-in result.errorssee the edit
Added sinceA small documentation edit on Deploy self-hosted environments to production touched a line naming claude auth login after this was published.* **Interactive `claude auth login`**: signs in through `claude.ai`, `claude.com`, and `platform.claude.com`. The [guided setup](/docs/en/self-hosted-environments-quickstart#run-the-guided-setup), `doctor`'s signed-in mode, and [CI dispatc…self-hosted-environments-deploysee the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesA small documentation edit on Deploy self-hosted environments to production touched a line naming claude auth login after this was…
