I’m working on an open-source thing that lets you co-draw diagrams with an LLM inside draw.io/diagrams.net.
You can ask the model to rough out an AWS/GCP/Azure architecture, but the key part is the loop: you still have the normal editor, so you drag boxes, rename stuff, add your own bits, and then say things like “clean this up”, “split this service out”, “add a read replica here”. The AI edits the real draw.io XML, it’s not just generating a picture, so you and the model are basically sharing the same canvas.
It can also try to rebuild a diagram from a screenshot/PDF and then you keep iterating together in chat + manual edits.
Recently I added “bring your own API key” for a bunch of providers and support for uploading PDFs/text to turn existing docs into diagrams.
You can ask the model to rough out an AWS/GCP/Azure architecture, but the key part is the loop: you still have the normal editor, so you drag boxes, rename stuff, add your own bits, and then say things like “clean this up”, “split this service out”, “add a read replica here”. The AI edits the real draw.io XML, it’s not just generating a picture, so you and the model are basically sharing the same canvas.
It can also try to rebuild a diagram from a screenshot/PDF and then you keep iterating together in chat + manual edits.
Recently I added “bring your own API key” for a bunch of providers and support for uploading PDFs/text to turn existing docs into diagrams.
Repo (just crossed ~10.2k): https://github.com/DayuanJiang/next-ai-draw-io Demo: https://next-ai-drawio.jiang.jp/
If you live in drawio a lot, I’d be curious where this breaks down or feels more annoying than just doing it by hand.