MockFlow Bridge: use your own AI agent on your MockFlow board

MockFlow Bridge connects the AI agent you already use to your MockFlow board. Claude Code, Codex, opencode or the built-in BridgeAI becomes the engine behind Mida. You keep working on the board as usual, while your own agent does the thinking on your computer and the result is drawn live on the canvas.

Two things make this different from asking Mida directly:

• It can read your local files. Point Bridge at a folder and your agent can build boards from your source code, specs, notes and transcripts. The files are read on your computer and are never uploaded. Only the finished drawing is saved to your board.

• It spends no MockFlow AI credits. The work runs on your own AI plan, so you are limited only by that plan.

What you can do with MockFlow Bridge

Most uses start with something already on your machine. Here are examples of what teams ask for, in their own words:

• Understand an unfamiliar codebase: "Make a mind map of how the payments module is structured." The map is drawn from the real source, not from an old wiki page.

• Draw architecture that matches what is deployed: "Draw the cloud architecture from our Terraform in infra/." The diagram comes from the files that define the infrastructure, so it is correct on the day you draw it.

• Lay out a database you inherited: "Read the migrations in db/ and lay out the entity relationships."

• Trace a request across services: "Draw a swimlane of what happens between checkout and fulfilment."

• Wireframe a screen from its spec: "Wireframe the notification settings screen from docs/notifications.md." An editable wireframe is on the board in under a minute, ready to mark up.

• Prepare an incident review: "Build a timeline of what happened from these log excerpts."

• Turn a meeting into decisions: "Here is the transcript from this morning's planning call. Turn it into a board of decisions, owners and open questions."

• Think through a new idea: "I am considering a subscription tier for small teams. Help me think it through visually." Delete the branches that do not fit and ask it to go deeper on the rest.

• Map anything with geography in it: "Map our accounts from customers.csv, then draw the three sales territories we are considering."

You do not need to name a component. Describe what you are working out and the agent picks the right form: a mind map, flowchart, kanban, timeline, chart, wireframe or map. Follow-up requests such as "add a Blocked column to that kanban" change the existing item in place instead of drawing a second copy.

How to set up MockFlow Bridge

You need Node.js 18 or newer, a MockFlow board open in your browser, and one AI to do the thinking. Claude Code, Codex and opencode are fully supported. If you do not use any of them, BridgeAI is built into Bridge and works with an API key from a provider such as OpenRouter.

1. Install Bridge once. Open Terminal (macOS) or Command Prompt (Windows) and run:

npm i -g @mockflow/mockflow-bridge

2. Start Bridge. Run it every time you want to use it, and leave the window open. It shows a pairing code.

mockflow-bridge

3. Pair your board. On the board, open Ask Mida, click Connect Local Agent at the top and enter the pairing code. The button turns green and names the connected agent. You pair once per computer.

4. Ask Mida as usual. The reply and the drawing now come from your own agent.

How to let your agent read local files

File access is off by default, so the agent cannot see anything on your computer until you choose a folder. To give it one folder, such as a repo or a folder of meeting notes, start Bridge with --workspace:

mockflow-bridge --workspace ~/Documents/my-project

The terminal confirms it with File access is ON and the folder it can read. Then ask about the files in plain words:

• "Read this folder and draw the project structure as a mind map"

• "Turn the meeting notes in this folder into a summary board"

• "Read the README and wireframe the main screens it describes"

The agent reads only that folder, only on your computer. Nothing in it is uploaded to MockFlow; only what it draws on the board is saved. To read a different folder, stop Bridge with Ctrl + C and start it again with the new path.

Everyday Bridge commands

mockflow-bridge status    # is it running, which boards are connected
mockflow-bridge agent     # show or change which AI answers
mockflow-bridge update    # install the newest version
mockflow-bridge help      # all commands and options

If more than one assistant is installed, the first start asks which one to use and remembers your choice. You can switch at any time without pairing again.

Use the board from Claude Code or Codex

If you prefer to work in your terminal, the MockFlow plugins for Claude Code and Codex connect those assistants to the same Bridge. Think an idea through in the conversation and watch the mind map, plan, architecture or screens appear on your board. The assistant reads the board too, so you can rearrange items, delete a branch or add a note, then ask it to continue from what is there.

Install the Claude Code plugin:

/plugin marketplace add mockflow/mockflow-claude-plugin
/plugin install mockflow@mockflow

Install the Codex plugin:

codex plugin marketplace add mockflow/mockflow-codex-plugin
codex plugin add mockflow@mockflow

What you end up with is an ordinary MockFlow board. Share the link and teammates open it in the browser, move things around and leave comments, with no plugin or terminal needed.

MockFlow Bridge on each plan

Bridge is free to install. On Basic it runs Claude Code on one board, with 20 generations a day. Bridge Pro, included in Plus and Max, removes the limit and adds every agent, several boards at once and local file access. On Max your agent can also reach your connected data sources, for example "Pull my open Jira tickets and lay them out as a kanban". See pricing for details.