Claude Design through the bridge
The bridge drives Claude Design in your own logged-in Chrome. Your agent sends a prompt and gets the reply text back, not the page.
- host
- claude.ai/design
- provider id
- design
- default model
- Claude Design
- start page
- https://claude.ai/design
What the bridge can do here
- Send a prompt in your logged-in Chrome and read the reply back as text.
- Pick a model. The default is Claude Design.
Example
$ bridge ask --provider design "Review this migration"MCP tools for Claude Design
design_state: Where Claude Design is: home or project page, project, model + effort, whether a turn is running, open Design tabs, the actions available here, and the Share destinations left to you.design_list_projects: List Claude Design projects (or design systems) with id, name, url, sharing.design_catalog: Choices for new work: home templates, models with effort levels (incl. More models), and design systems.design_choose_model: Pick the model (incl. More models) and effort in a project's composer, or on home for new projects. Like the UI, it becomes your Claude Design default.design_list_files: List the files in a Design project.design_read_conversation: Read a project's Conversations and the latest messages — what you asked and what Claude replied.design_open_project: Open (or focus) the project's tab in the bridge Chrome.design_create_project: Create a Design project. With a prompt: home composer with optional template, model, effort, and attachments, then wait for Claude's first reply. Without: a blank project.design_send: Send a message in a project's Conversation (optional model, effort, design systems, attachments) and return Claude's reply. status is replied, running, or waiting-for-answer. For long turns pass wait:false, then poll design_read_conversation.design_new_conversation: Start a new Conversation in a project and return its id.design_rename_conversation: Rename a Conversation in a project.design_update_project: Rename a project, star/unstar it, or set its design systems.design_duplicate_project: Duplicate a project and return the copy's id.design_delete_project: Permanently delete a project (requires confirm:true).design_put_files: Add repo files to a project; an existing path is replaced.design_remove_files: Delete files from a project (requires confirm:true).design_download: Download project files, or the whole project as a zip, into the repo (.bridge/downloads/design by default).design_share: Set who can open the project (private or workspace, with view/comment/edit) and return its link.
Claude Design support
The bridge drives Claude Design, Claude's project workspace for slides, prototypes, and documents, from your signed-in bridge Chrome. Reads and project/file changes use the app's own requests instead of the UI; turns, templates, and model/effort go through the real UI, one tab per project.
bridge chrome start --provider design # sign in at claude.ai bridge design catalog # templates, models + effort levels, design systems bridge design projects --query launch # list / search projects (--design-systems for design systems) bridge design model --model "Sonnet 4.6" --effort Low # pick model (incl. More models) + effort; --project for a project bridge design create --template Slides --prompt "our Q3 launch" --model "Haiku 4.5" --effort Low bridge design send --project <id> --message "make the title bolder" --model "Sonnet 4.6" --attach brief.md bridge design read --project <id> # Conversations + latest messages (what you wrote, what Claude replied) bridge design new-conversation --project <id> bridge design rename-conversation --project <id> --conversation <cid> --title "Logo pass" bridge design files --project <id> bridge design put --project <id> --file hero.png --dir assets # add, or replace the same path bridge design rm --project <id> --path assets/old.png --yes bridge design download --project <id> # project files to <repo>/.bridge/downloads/design/<id> bridge design export --project <id> # the project .zip bridge design share --project <id> --access workspace --permission comment bridge design rename --project <id> --name "Launch deck" bridge design duplicate --project <id> bridge design favorite --project <id> # --off removes the star bridge design use-design-systems --project <id> --design-system <dsid> # --none clears them bridge design delete --project <id> --yes bridge design state # where Claude Design is, busy tabs, available actions
Add --json to any verb for machine-readable output. send and create wait for Claude's reply (--timeout, default 600 s); --no-wait returns while the turn runs and --auto-decide answers clarifying questions with "Decide for me". A model or effort choice also becomes your Claude Design default, exactly as when you pick it in the UI.
Agents get the same surface as design_* MCP tools over bridge serve: design_state, design_list_projects, design_catalog, design_choose_model, design_list_files, design_read_conversation, design_open_project, design_create_project, design_send, design_new_conversation, design_rename_conversation, design_update_project, design_duplicate_project, design_delete_project, design_put_files, design_remove_files, design_download, design_share. Destructive tools (design_delete_project, design_remove_files) require confirm: true; local paths must stay inside the target repo.
Left to you in the UI: Publish as artifact, Send to Claude Code, PNG/video/PDF/PowerPoint export, partner app exports, comments, and version restore; design state lists them. Design is not a Fan-out provider: a Fan-out tab closes when its task ends, which would cancel the turn.