Open Design

View saved version →

---
name: open-design-mode
description: Create and refine websites, slides, prototypes, and design systems through the local Open Design MCP. Use Open Design Cloud by default, or Local Codex and secure BYOK only when the user explicitly selects them.
---

# Open Design execution mode

Use this workflow whenever a user asks the Open Design plugin to create
or continue an artifact.

## Required local boundary

All modes use the independently registered local `open-design` MCP server. The
plugin does not include an MCP transport and does not call a remote MCP domain.

Open Design must be installed, but its Electron window does not need to be
open. A packaged MCP registration starts the signed Open Design runtime
headlessly when its daemon is stopped.

If `open-design` is unavailable:

1. Check whether Open Design is installed and whether an `open-design` MCP
   registration already exists. Preserve all unrelated MCP servers.
2. If Open Design is missing, ask the user before opening the official download
   page at `https://open-design.ai/download/`. Do not silently download or
   execute an installer, and do not use an unverified install script.
3. If Open Design is installed, use its resolved signed packaged executable
   with `--headless --mcp-install codex`, or use the `od mcp install codex`
   operation supplied by that installation. Do not guess a source checkout
   path, a localhost URL, or run the unrelated macOS `/usr/bin/od` utility.
4. Verify `codex mcp get open-design --json`. If the current Codex task cannot
   hot-load the new MCP snapshot, tell the user to start one new task.

## Choose the mode

Open Design Cloud is the default mode. It uses the local Open Design daemon and
its bundled cloud runtime. Local Codex and BYOK are available only when the
user explicitly selects them.

Resolve the execution mode from the user's current request before calling
`collect_brief`. An explicit choice such as Local Codex, Open Design Cloud, or
secure BYOK remains selected through Brief collection, confirmation, project
selection, generation, polling, and terminal delivery for that logical
generation.

Never silently switch modes because authentication, balance, transport, quota,
or generation failed. Explain the failure and offer the user applicable
choices, such as retrying the selected mode, completing its authentication, or
switching to another available mode. State when the alternative uses an Open
Design Cloud account or a BYOK provider account. Switch only after the user
explicitly confirms the new mode.

After an explicit switch, start a new execution context and request identifier.
Reuse only the human-readable confirmed brief; never repeat its signed machine
envelope. The selected mode may change between logical generations, but one
logical generation must never drift between modes.

## Keep implementation names out of user-facing copy

Match status updates, errors, and final delivery prose to the language of the
user's current request. In user-facing text, use only these product terms:
Open Design Cloud, Local Codex, secure BYOK, and Open Design Cloud account or
credits.

Some MCP tool names and machine parameters below retain compatibility
identifiers such as `get_vela_login_status`, `start_vela_login`, and `amr`.
Treat them as machine-only protocol values. Never quote, explain, or expose
those identifiers, raw agent selectors, internal endpoints, or service account
names in user-facing prose. Translate tool errors into the product terms above
without changing the actual MCP argument values.

Before every `collect_brief` call, derive a normalized BCP-47 `locale` from the
language of the user's current message and pass it to the tool. For example,
use `zh-CN` for a Simplified Chinese request and `en` for an English request.
Use the Host UI locale only when the current message language is genuinely
indeterminate, then fall back to `en`. Keep question ids, option values,
artifact types, and other machine fields unchanged 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 2 — file references are metadata, not package contents.