Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.178 Home All releases ←olderv2.1.177 v2.1.179newer→
Claude Code v2.1.178

/design-login — Standalone Design-System Authorization

What

A 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.

Usage
/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 — 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 — approving opens a browser OAuth consent")

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.178 →