{"version":"2.1.178","anchor":"design-login-standalone-design-system-authorization","canonical_anchor":"design-login-standalone-design-system-authorization","heading":"\/design-login \u2014 Standalone Design-System Authorization","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.178\/e\/design-login-standalone-design-system-authorization","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.178","markdown":"### \/design-login \u2014 Standalone Design-System Authorization\n\n**What**\n\nA new slash command that authorizes design-system (claude.ai\/design) access independently of the main session login. This is especially useful when Claude Code authenticates via an API key or provider token rather than a claude.ai subscription.\n\n**Usage**\n\n`\/design-login` **Details** - Opens a browser OAuth consent page specific to design-system scopes (`user:design:read`, `user:design:write`) - On SSH or remote sessions (where a browser can't reach the local listener), the flow falls back to a manual code-paste method - The credential is stored as a separate `designOauth` entry in settings, entirely separate from the main session token \u2014 signing out of claude.ai does not invalidate the design credential - The credential auto-refreshes; if a refresh fails the command re-prompts - Requires `CLAUDE_CODE_DESIGN_OAUTH_CLIENT_ID` to be set (or a build that includes the registered client id) - A 5-minute browser-authorization timeout applies; after that, the manual `\/design-login` flow is suggested **Evidence** Design OAuth lock and flow (search for `\"Design login\"`, `\".design_oauth_refresh.lock\"`, `\"design login \u2014 approving opens a browser OAuth consent\"`)"}