{"version":"2.1.248","anchor":"claude-design-explains-a-rejected-credential","canonical_anchor":"claude-design-explains-a-rejected-credential","heading":"Claude Design explains a rejected credential","tier":"use","area":"Claude Design","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/claude-design-explains-a-rejected-credential","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Claude Design explains a rejected credential\n\nIf your credential lacks Claude Design access, you're told to run \/design login.\n\n**What**\n\nIf 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.\n\n**Details**\n\n- 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\n- Reachable only in sessions where the Design tool is present; nothing in this build shows what turns it on\n\n**Evidence**\n\n`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.`\n\n- Area: Claude Design\n- Names: `\/design login`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}