{"version":"2.1.247","anchor":"a-design-credential-missing-the-right-scopes-now-says-so","canonical_anchor":"a-design-credential-missing-the-right-scopes-now-says-so","heading":"A Design credential missing the right scopes now says so","tier":"notice","area":"Design","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/a-design-credential-missing-the-right-scopes-now-says-so","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### A Design credential missing the right scopes now says so\n\nA Design credential lacking permissions now says so and tells you to run \/design login.\n\n**What**\n\nWhen the Design API rejects a request with HTTP 403 and the body `error: \"needs_design_scopes\"`, Claude Code now reports that the stored credential lacks Design permissions and tells you to run `\/design login`, rather than showing a generic authentication failure.\n\n**Details**\n\n- Raised as a distinct error carrying the code `design_tool_needs_design_scopes`.\n- Non-interactive sessions get a longer message explaining that a CI runner has to reuse a login stored earlier.\n- The MCP side of Design got a matching 403 message pointing at `\/design-login`.\n- Applies to every 403 with that body; no flag involved.\n\n**Evidence**\n\n`design_tool_needs_design_scopes`\n\n- Area: Design\n- Names: `\/design login`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}