A Claude Design 403 now says whether your credential actually grants access.
What's wrong with this entry?
When Claude Code's built-in Claude Design connection is rejected with HTTP 403, the message now depends on whether your current credential actually grants Claude Design access. If it does, you get "rejected your Claude Design credential (HTTP 403)" rather than the older wording that blamed your claude.ai login for lacking access.
- Access is determined by the presence of the
user:design:readpermission on the credential, or by holding a design-specific credential.
user:design:read
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.229
New /design skill drafts multi-artboard canvases as an Artifact, gated off
Both mention design
-
v2.1.235
Claude Design state moved off module globals onto a per-session object
Both mention design
-
v2.1.238
A
/designcommand that drafts a design on a canvas artifactBoth mention design