{"version":"2.1.199","anchor":"claude-design-integration-gradual-rollout","canonical_anchor":"claude-design-integration-gradual-rollout","heading":"Claude Design Integration [Gradual Rollout]","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.199\/e\/claude-design-integration-gradual-rollout","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.199","markdown":"### Claude Design Integration [Gradual Rollout]\n\n**What**\n\nA new `ClaudeDesign` tool that lets Claude work directly with claude.ai\/design \u2014 a collaborative canvas for decks, prototypes, landing pages, and UI mockups backed by your team's design system.\n\n**Usage**\n\n`\/design login # Authenticate with claude.ai for Design access \/design consent # Grant Claude agent access to your Design projects \/design <prompt> # Route to Design operations (import, export, status, etc.)` **Details** - Operations include: `list_projects`, `read_file`, `write_files`, `delete_files`, `finalize_plan`, `get_claude_design_prompt`, `render_preview`, and more - Write operations (`write_files`, `delete_files`) require a `plan_token` obtained from `finalize_plan` first - Requires a claude.ai credential \u2014 not available via Bedrock, Vertex, or third-party providers - First-party Design server has a consent gate: the user grants Claude agent access once per account; `\/design consent` handles this - Not available when `nonessential network traffic` is restricted **Status** Feature-flagged (`tengu_omelette_fouet`) \u2014 rolling out gradually.\n\n**Evidence**\n\nClaudeDesign tool (search for `\"ClaudeDesign\"`, `\"\/v1\/design\/mcp\"`, `\"claude.ai\/design\"`)"}