If your credential lacks Claude Design access, you're told to run /design login.
What's wrong with this entry?
If claude.ai credentials do not carry Claude Design access, the tool now says so directly and tells you to run /design login, with separate wording for non-interactive sessions such as CI or hosted runs where that command cannot be used.
- Accompanied by new error types for missing consent and missing project access, and a validation table for Design tool arguments including list_projects, write_files and register_assets
- Reachable only in sessions where the Design tool is present; nothing in this build shows what turns it on
Claude Design rejected this session's claude.ai credential (HTTP 403): it does not carry Claude Design access. Run /design login to authorize Claude Design, then retry.
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.229
New /design skill drafts multi-artboard canvases as an Artifact, gated off
Both mention design