vibeflow kanban.
Board, overlay, one process.

Q: Port 3700 is already taken.

Pass `-p, --port` — for example `npx @vibeflow-tools/cli kanban -p 4100`. The board, the overlay script and the task API all follow the port you choose.

Q: Can someone else on my LAN use the board?

Only if you opt in: `--host 0.0.0.0` binds the server to your LAN address instead of localhost. The board and task API are then reachable in your network — while the MCP endpoint still refuses non-loopback requests unless an auth token is configured.

One command starts the local server on port 3700, opens the live Kanban board and serves the annotation overlay your app loads. Tasks, screenshots and the board all stay on your machine.

Quick start

Run it, then point the overlay at your app.

01 Start

Start the server.

The optional directory argument selects the project root (default .) — that is where .vibeflow/ lives. The board opens at localhost:3700/kanban.

Overlay script — /vibeflow-overlay.js on the same server.
Injection snippets — bookmarklet, script tag and console snippet at /inject.
Agent prompt — the CLI prints the exact tasks --next line to paste into your agent.

terminal

$ npx @vibeflow-tools/cli kanban

✓ Kanban board ready

http://localhost:3700/kanban

Flag reference

Flags.

Run npx @vibeflow-tools/cli kanban --help for the canonical list.

vibeflow kanban flags
Flag	What it does
Usage
`[dir]`	Project root directory — where `.vibeflow/` lives (default `.`).
Options
`-p, --port <port>`	Port number (default 3700).
`--host <host>`	Bind hostname — default localhost; use `0.0.0.0` for LAN sharing.
`--no-open`	Do not open the browser automatically.
`--no-changelog`	Do not show the changelog with the update notice.

The overlay

Three ways to inject, no extension.

While the server runs, visit localhost:3700/inject for ready-to-use snippets of all three.

Overlay injection methods
Method	Best for	CSP-safe
Bookmarklet (recommended)	Any page, including production apps	Yes
Script tag	Pages you control the HTML of	No
DevTools console	Quick one-off sessions	Yes

On the same server

What else answers on port 3700.

The live board at /kanban — drag cards, open tasks, attach files; updates sync over WebSocket.
The task API — /api/tasks and the tRPC surface the overlay writes to.
The MCP endpoint at /api/mcp — expose the same tasks to any Model Context Protocol client (see the MCP setup guide).
Screenshots captured by the overlay, served back to the board from /screenshots.

If something looks wrong

Common questions.

The board opens, but my app has no overlay.

The overlay is served from the running server, so the server must stay up. Add the script tag before </body>, or drag the bookmarklet from /inject onto your bookmarks bar. If the browser console shows a blocked request, your content security policy is rejecting another origin — allow localhost:3700.

Port 3700 is already taken.

Pass -p, --port — for example npx @vibeflow-tools/cli kanban -p 4100. The board, the overlay script and the task API all follow the port you choose.

Can someone else on my LAN use the board?

Only if you opt in: --host 0.0.0.0 binds the server to your LAN address instead of localhost. The board and task API are then reachable in your network — while the MCP endpoint still refuses non-loopback requests unless an auth token is configured.

How to use Vibeflow — the three-step workflow from annotation to merge
vibeflow tasks — the full flag reference for the agent command
vibeflow serve — prototypes and API-only mode
MCP setup guide — connect an MCP client to this server
Give your AI agent UI context — why pointing beats describing

Ten seconds to your
first annotated task.

No account, no cloud, no browser extension.

Get started free Star it on GitHub

Apache-2.0 · Node.js 22+ · tasks stay in your repository

vibeflow kanban.Board, overlay, one process.