Cloud gateway sign-in check reworked with a clearer error and desktop-app-aware handling
Before using the Cloud gateway as its provider, Claude Code now checks three things instead of one: that the route is actually set to gateway, that there's no gateway authentication, and that no gateway server process is running. Previously it only checked a single administrator-policy condition.
The error message shown when not signed in now reads: "Not signed in to the Cloud gateway - run /login. (With CLAUDE_CODE_USE_GATEWAY, set ANTHROPIC_BASE_URL and ANTHROPIC_AUTH_TOKEN.)" — pointing to those environment variables as an escape hatch. It also now shows a distinct error when credentials are managed by the desktop app instead.
This gives a more accurate check for whether the Cloud gateway is actually usable, and a clearer error message that tells users how to work around a sign-in problem using environment variables, or explains that their desktop app is managing credentials instead.
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.
* **Amazon Bedrock, Google Cloud's Agent Platform, or Claude Platform on AWS**: add `ANTHROPIC_AUTH_TOKEN` after the block. Claude Code sends it to the gateway as an `Authorization: Bearer` header. For a credential in a different scheme or…llm-gateway-connect see the edit
* Fixed every turn failing with HTTP 400 on third-party Anthropic-compatible endpoints (`ANTHROPIC_BASE_URL`) since 2.1.265: a regex in the Artifact tool's input schema that those endpoints rejectchangelog see the edit
Anthropic's documentation has since written up ANTHROPIC_BASE_URL, on Claude Code changelog.
Fixed /login showing "no gateway URL is configured" when re-run in a session that signed in to a Claude apps gateway set by managed settings