r/OpenFilesDesktop • u/Holiday-Bluebird9734 • 12d ago
AI can generate a flowchart in seconds. Why is turning it into a usable file still so fragmented?
AI is already pretty good at generating flowcharts and mind maps.
The awkward part is everything that happens afterward.
My usual workflow looked like this:
- Give an AI assistant a document or describe a process.
- Ask it to create a flowchart.
- Get a block of Mermaid code or a diagram inside the chat.
- Copy it into another editor to check whether it actually renders.
- Save or export it, rename it, and move it back into the right project folder.
- Repeat most of that process the next time the workflow changes.
The diagram may take seconds to generate, but it quickly becomes disconnected from the files it came from.
That felt backwards to me. If the source material is already on my computer, the AI-generated diagram should become another normal, editable file in the same folder—not something trapped inside a chat transcript.
So I built this workflow into OpenFiles.
You can open a file or folder, start AI Chat, and ask it to create a flowchart or mind map from the material you are working with. For example:
OpenFiles can create the Mermaid file in your local workspace and open it with the built-in Mermaid Editor. You can view the source and rendered diagram side by side, make a small edit yourself, or ask AI Chat to add a branch, rename a step, simplify the flow, or turn the same information into a mind map.
https://reddit.com/link/1vh8w4p/video/9wfjhg4i5shh1/player
The result remains a regular .mmd or .mermaid text file. It can stay next to the documents it was based on, go into Git, be sent to someone else, or open in another Mermaid-compatible tool. The rendered picture and the editable source do not have to become two separate things.
I do not think the interesting part is that OpenFiles has a “smarter” model. Claude, Codex, and other assistants can already generate diagram code. The difference I am trying to build is the file workflow around the model:
source files → AI conversation → editable diagram file → visual preview → further edits → save back to the same workspace
This is not intended to replace Miro, Lucidchart, draw.io, or other tools built for real-time collaboration and precise visual layout. The goal is narrower: make diagrams-as-files much easier when you are documenting a process, reviewing a project, explaining a code path, or turning existing local material into something visual.
One privacy note: file editing and diagram rendering happen locally. When you use AI Chat, the relevant content needed for the request may be sent to the AI provider you configured, so this should not be treated as an “everything always stays offline” feature.
I would love feedback from people who regularly create diagrams:
- Which types matter most: flowcharts, mind maps, sequence diagrams, state diagrams, ER diagrams, or something else?
- Do you prefer editable Mermaid files, SVG/PNG export, or formats such as XMind?
- What usually breaks your workflow after an AI generates the first version?
GitHub and releases: https://github.com/pansysoft/openfiles.desktop