What
When the Claude Design connector rejects your token, the message now depends on what was sent: no credential at all, a /design-login credential, a claude.ai login that already carries Design permissions, or a plain login. That points you at /design-login or /login specifically instead of one generic failure.
Details
- Applies whenever first-party MCP authentication is rejected.
Evidence
even though that login already includes Claude Design permissions
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundle/design-login/login
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.
Added since
A small documentation edit on Claude Code on Claude Platform on AWS touched a line naming /login after this was published.
The `/login` and `/logout` commands don't sign you into a claude.ai subscription for Claude Platform on AWS. Authentication runs through your AWS credentials or workspace API key.claude-platform-on-aws see the edit
Added since
A small documentation edit on Claude apps gateway for Amazon Bedrock, Claude Platform on AWS, Google Cloud, and Microsoft Foundry touched a line naming /design-login after this was published.
| [`/design-sync`](/docs/en/commands#all-commands) and `/design-login` | Not available | Both need claude.ai, which the CLI doesn't contact on gateway sessions, so neither command appears there |claude-apps-gateway see the edit
Confirmed since
Anthropic's documentation has since written up /login, on Claude Code changelog.
* Added the `gatewayInternalNetworks` managed setting, letting administrators allow `/login` to a Claude apps gateway on their organization's own public IPv4 blockchangelog see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /login, on Claude Code changelog.