Design login failures now tell you whether to run /design-login or /login.
What's wrong with this entry?
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.
- Applies whenever first-party MCP authentication is rejected.
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.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.247
Design login errors explain how headless runs inherit authorization
Both mention design login
-
v2.1.247
A Design credential missing the right scopes now says so
Both mention design login
-
v2.1.248
Claude Design explains a rejected credential
Both mention design login