{"version":"2.1.280","anchor":"design-tool-auth-failures-now-redirect-to-design-login-inste","canonical_anchor":"design-tool-auth-failures-now-redirect-to-design-login-inste","heading":"Design tool login failures now point users to \/design login","tier":"notice","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/design-tool-auth-failures-now-redirect-to-design-login-inste","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Design tool login failures now point users to \/design login\n\nDesign tool authentication errors are now classified and redirect users to log in to Claude Design specifically\n\n**What**\n\n- When a `claude.ai` credential lacks access to Claude Design, the resulting error now carries a structured tag `{kind: \"auth_missing_scope\", provider: \"claude_design\"}` instead of just a name, for more consistent error handling.\n\n- When the design tool's credential check fails because the user needs to log in (`needs_design_login`), the client now throws a specific `design_needs_authorization` error (provider `claude_design`) instead of a generic `design_tool_auth_failed` error.\n\n**Why** This lets the interface recognize design-specific authentication problems and send users straight to `\/design login` instead of showing a generic failure message.\n\n- Area: Artifacts\n- Names: `\/design`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}