Which way in matters most to you?
by•
OpenFlowKit 2 has five ways to make a diagram: draw it, write it as code (or paste Mermaid, D2, Structurizr), ask any AI model or a local one, let Claude Code edit it over MCP, or map a GitHub repo with every arrow cited to a file and line.
If you could only keep one, which would it be, and what's missing from it? This decides what I build next.
63 views
Replies
The local model option would be useful for private projects. I wouldn't always want to send internal architecture details to an external model.
@qinuo_yang Exactly why it’s there. Diagrams stay local-first in your browser, and with a local model your architecture never leaves your machine. What do you run locally, Ollama or LM Studio? I’d love to know how it holds up on a real internal project.
Nice take! I've been through this when a diagram looked right but it was already describing an older version of the system, which is worse than not having one because everyone trusts it. What I ended up doing was keeping architecture changes small and forcing a second pass that points each important decision back to the code or a test. It makes the flow a bit slower, and I’m actually divided on how much layout should be automated, but the review becomes much less guesswork. How do you decide when a proposed change is trustworthy enough to land?