Update to MockFlow

{
  "description": "Check, pair or troubleshoot the connection between this machine and a MockFlow board. Use when board tools are missing or failing, when nothing appears on the board, or when the user asks which board they are connected to.",
  "included_files": [],
  "name": "connect",
  "skill_md_contents": "---\nname: connect\ndescription: Check, pair or troubleshoot the connection between this machine and a MockFlow board. Use when board tools are missing or failing, when nothing appears on the board, or when the user asks which board they are connected to.\n---\n\n# MockFlow connection\n\nThree things have to be true before anything can be drawn: the bridge helper is\ninstalled, a daemon is running, and a board tab is paired.\n\nWork through them in that order. Each check tells you which one failed. But check\nstep 0 first, because when it fails the other three are unreachable and every fix\nbelow is wasted effort.\n\n## 0. Can this session reach the user's own computer?\n\nEverything else here assumes the session is running on the machine the board tab\nis open on. When it is not, the bridge cannot be reached from here at all, and\nsaying \"start the bridge\" sends the user off to fix something that was never the\nproblem.\n\nTwo environments where this is the case:\n\n- **ChatGPT, web or desktop.** A ChatGPT conversation runs on OpenAI's servers\n  even in the desktop app — ChatGPT and Codex share that app, and the selector\n  in the interface decides which one a conversation is. On the ChatGPT side\n  there is no shell on the user's machine and the plugin cannot carry its MCP\n  configuration, so the board tools are never present. Nothing the user\n  installs will make them appear.\n- **A cloud or remote container.** There is a shell, but it is not the user's\n  computer. The bridge and the board tab have to be on the same machine, so a\n  bridge started in a container has nothing to pair with.\n\nThe tell is that you have no way to run a command on the user's own machine. If\nthe MockFlow tools are absent and you cannot check for the bridge locally, assume\nthis rather than assuming a stopped daemon.\n\nSay it plainly, name Codex as the way forward, and stop:\n\n> Drawing on your board goes through **mockflow-bridge**, a small program that\n> runs on your own computer and talks to the board tab open in your browser. A\n> ChatGPT conversation runs on OpenAI's servers — even in the desktop app — so\n> it has no way to reach the bridge, and the board tools will not appear here\n> however long you wait.\n>\n> Switch to **Codex**. In the desktop app that is the selector in the same\n> interface; in a terminal it is the Codex CLI. A Codex session runs on your\n> machine, so it can reach the bridge. Install the plugin there, run\n> `mockflow-bridge`, and pair it with your board once.\n\nLead with the selector: for someone already in the desktop app it is the\nsmallest possible move, same app, same account, one switch. The Codex CLI is\nthe alternative for people who already work in a terminal. Someone in the web\napp needs both steps: the desktop app, then Codex selected inside it.\n\nBe precise that the desktop app alone is not the answer. ChatGPT and Codex live\nin the same app now, and the app with ChatGPT selected still cannot draw. Say\n\"select Codex\" every time, not \"use the desktop app\".\n\nDo not offer the npm command, do not offer to install anything, and do not fall\nback to a mermaid block or a text sketch as though the request had been met. If\nthey want something on a board right now without leaving the browser, Ask Mida on\napp.mockflow.com is the thing to point at.\n\n## 1. Is the helper installed?\n\n```bash\ncommand -v mockflow-bridge\n```\n\nNothing returned means it is not installed. Offer to install it and say what it\nis: a small local program, about 2MB, no MockFlow account required.\n\n```bash\nnpm i -g @mockflow/mockflow-bridge\n```\n\nIf Node.js itself is missing, that comes first, from nodejs.org, version 18 or\nnewer.\n\n## 2. Is a daemon running?\n\n```bash\nmockflow-bridge status\n```\n\nThis reports whether the daemon is up and which boards are connected. If it is\nnot running, start it. Nothing can be drawn without it, and the MockFlow tools in\nthis session will be unavailable until it is up and the session has reloaded.\n\n## 3. Is a board paired?\n\nThe daemon shows a **pairing code**. The user opens their board at\napp.mockflow.com, clicks **Connect Local Agent** at the top of Ask Mida, and\nenters that code. The button turns green.\n\nPairing is per computer and survives restarts, so this is a one time step. But\n**codes change every time the daemon restarts**, so an old code will be rejected.\nIf pairing fails, get the current code rather than reusing one from earlier in\nthe conversation.\n\n## Which board am I drawing on?\n\n`list_boards` shows what is connected. `select_board` pins the target explicitly.\nWithout an explicit selection, draws go to the tab the user is focused on, else\nthe only connected tab.\n\n## Nothing appeared on the board\n\nIn likelihood order:\n\n1. The board tab was closed or reloaded, so the pairing is gone. Re-pair.\n2. The daemon stopped. Check step 2.\n3. Draws went to a different connected board. Check with `list_boards`.\n\n## Reading files\n\nFile access is off by default. The daemon has to have been started with\n`--workspace <path>` for the agent it spawns to read a folder. This does not\naffect Claude Code reading files itself, only the Ask Mida side.\n"
}