{"version":"2.1.251","anchor":"design-login-errors-now-say-which-credential-was-actually-se","canonical_anchor":"design-login-errors-now-say-which-credential-was-actually-se","heading":"Design login errors now say which credential was actually sent","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/design-login-errors-now-say-which-credential-was-actually-se","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Design login errors now say which credential was actually sent\n\nDesign login failures now tell you whether to run \/design-login or \/login.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- Applies whenever first-party MCP authentication is rejected.\n\n**Evidence**\n\n`even though that login already includes Claude Design permissions`\n\n- Area: Auth\n- Names: `\/design-login`, `\/login`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}