@codecainecli/codecaine-cli

Connects the Codecaine web editor to your machine.

npx @codecainecli/codecaine-cli            # start it; opens the editor
npx @codecainecli/codecaine-cli ./my-app   # and open a project folder

While it runs, the editor in your browser can open and save project folders, keep pictures on disk, and frame your running app on the board through a local proxy, with no changes to the app. Everything stays on your machine. The companion listens on 127.0.0.1 only, and only the editor's own origin can connect to it.

Setting everything up

npx @codecainecli/codecaine-cli setup

Starts the companion in the background, downloads and starts its assistant (bb, its own copy, separate from the Codecaine desktop app's, on a Node of its own so it runs whatever Node you have), adds the MCP server to Claude Code when it is installed (--no-mcp skips that), and opens the editor. Safe to run again.

Your coding agent

claude mcp add codecaine-web -- npx -y @codecainecli/codecaine-cli mcp

codecaine-cli mcp is an MCP server on stdio, named codecaine-web so it is never taken for the Codecaine desktop app's own. Inside a bb thread (the desktop app's assistant) it offers no tools and starts nothing. It starts the companion if it isn't running and forwards to it, so every agent shares one companion. Ask your agent to run the project and open it in Codecaine. It starts the dev server and calls openProject, then edits the design with the editor's own tools.

HTTP clients can use http://127.0.0.1:4317/mcp with the bearer token the companion prints.

Options

| | | | --- | --- | | --editor <url> | The editor's address (default https://web.codecainehq.com) | | --origin <a,b> | More origins allowed to connect | | --port <n> | Default 4317 | | --no-open | Don't open the browser | | --no-assistant | Run without the assistant (bb); board requests go to MCP agents |

State lives in ~/.codecaine/web (CODECAINE_HOME to move it).