figcraft-editor

FigCraft embedded editor

1. Call the current plugin's open_editor, passing the absolute path of the task workspace on the first call. Supports MCP Apps hosts rendering the returned UI resource.
2. When it is not presented automatically, call open_browser_editor, open the actually returned editorUrlwith the host's built-in browser. Codex Desktop can use the browser target of open_in_codex ; do not guess the port.
3. Call editor_status and verify that the page is actually ready. Do not treat the returned URL or HTTP 200 as the screen having been opened.
4. Use only the editing tools listed by the same current service, and check the tool schema first. The official original Web and the enhanced Web differ in command and file capabilities; handle them according to the returned capabilities and version.
5. After editing with the enhanced version, save to a new path in the workspace, reopen, and check the structure and the screen. Official Web 0.6.0 has no file Services and cannot promise that the original page can save; native CLI sessions and the page are independent.
6. When the host supports only stdio MCP and not MCP Apps/built-in browser, it is clearly impossible to display it inside the host; an external browser does not count as acceptance for opening it internally.

Upstream Web implementation. The plugin's local candidate must first be built ui/dist/adapter.mjs. Do not install, upgrade, or change host settings to bypass missing capabilities.