{"version":"2.1.302","anchor":"design-consent-and-revoke-give-cloud-session-specific-error","canonical_anchor":"design-consent-and-revoke-give-cloud-session-specific-error","heading":"\/design consent and revoke failures in cloud sessions point to claude.ai settings","tier":"notice","area":"Claude Design","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/design-consent-and-revoke-give-cloud-session-specific-error","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### \/design consent and revoke failures in cloud sessions point to claude.ai settings\n\nWhen `\/design` consent or revoke fails in a cloud session, the error now sends you to claude.ai\/design\/settings instead of `\/design-login`\n\n**What**\n\nThe `\/design` command can grant or revoke the Design agent's access to your Claude Design projects. When either step fails in a cloud session, which is a Claude Code session running remotely rather than on your own computer, Claude Code now shows a separate message:\n\n- A failed grant says it could not record access from this cloud session, and tells you to grant it at claude.ai\/design\/settings and then retry your Design request.\n\n- A failed revoke says it could not revoke access from this cloud session, and tells you to revoke it at claude.ai\/design\/settings.\n\nOutside cloud sessions the error is unchanged and still suggests running `\/design-login`. A successful grant now also shows an extra line after the success text.\n\n**Why**\n\n`\/design-login` is not a usable fix inside a cloud session, so the old message sent people to a step they could not take. The new message gives them a place that works.\n\n- Area: Claude Design\n- Names: `\/design`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}