OpenFlowKit 2 - Free, open-source diagrams you and your agent edit together

by•
A free, open-source diagram canvas: MIT, local-first, no account, in your browser. One canvas, five ways in. Draw it. Write it as code, or paste Mermaid, D2 or Structurizr. Ask any of 10 AI providers, or a local model. Hand it to your coding agent: Claude Code edits the canvas you have open, live, over MCP. Or pull it from a GitHub repo, every arrow citing its file and line. The CLI checks drift in CI, so diagrams keep up with your code.

Add a comment

Replies

Best
Hi everyone, I'm Varun. OpenFlowKit was here about 8 months ago as v1. Version 2 is a rebuild from scratch: - One canvas, five ways in: draw it, write it as code, ask any AI model (or a local one), hand it to your coding agent, or pull it from a GitHub repo - Your coding agent edits the canvas you have open, live, over MCP (npx -y openflowkit mcp). Every change is one undo step - Text and canvas are the same diagram: write it as code, or paste Mermaid, D2 or Structurizr - The repo map cites the file and line behind every arrow, so you can check it instead of trusting it Why I built it: every team I've worked on had an architecture diagram that was right once. The code kept moving, the diagram didn't, and new people learned the system from a picture nobody trusted. So everything here is built to keep the diagram current: you, your AI and your agent all edit the same one. Try it with no account: app.openflowkit.com Honest limits: the map reads code statically (imports and config files, not running traffic), reads public GitHub repos in the browser (run the CLI on a checkout for private ones), and is weaker on .NET and Elixir projects without containers. There's no real-time collaboration yet. It's free and MIT licensed, and I built it on my own. A real question: what's the diagram you keep redrawing? Try it there and tell me what got in the way.