coart-open-canvas

Coart Open Canvas

Use this workflow whenever the user asks to open or reopen Coart for the active project.

Current runtime

Coart v0.3.0 is TypeScript-first:

• Node.js 22.6+ executes scripts/start-mcp.ts directly with type stripping.
• The stdio entrypoint imports mcp/server.ts; do not refer to removed .mjs entrypoints.
• The in-task MCP Apps Widget is the default editing surface. It is bound to the requested project and writes only to <projectDir>/canvas/.
• open_coart_editor remains available for an explicitly requested standalone Chrome／Edge app window, served from a token-protected loopback bridge.

Default open procedure

1. Call render_coart_canvas with the absolute active project path and displayMode: "sidebar" so the canvas opens in the Codex task sidebar:

   {
     "projectDir": "C:/work/my-project",
     "displayMode": "sidebar"
   }
   

2. Keep the project path unchanged. The snapshot, selection, view state, references, and generated assets are persisted under <projectDir>/canvas/; never substitute the plugin cache path.

3. The Widget's generation and annotation controls use the Codex Apps sendMessage bridge. Treat the resulting message as a normal user follow-up and continue the image/HTML/Slides workflow in this conversation; never ask the user to copy or paste a prompt.

4. When the user finishes editing, call get_coart_latest_image to return the newest project-local image as MCP image content, or call read_coart_asset when the user names a specific asset. Keep the original asset unless the user explicitly requests replacement.

5. If the user explicitly asks for the standalone editor, call open_coart_editor. Its follow-up controls write a project-local pending request; after the user says "繼續處理" or otherwise returns to the conversation, call get_coart_pending_request, handle the request, then call clear_coart_pending_request after success. Do not ask the user to paste the prompt.

Sidebar Widget (default) and inline fallback