Includes:
- AI Copilot for diagram generation
- Auto layout + smart connectors
- Multi-model support (GPT / Gemini / Claude)
- Ready-to-install Windows package (.exe / .msi)
Draw Diagrams by using ai-drawio-copilot - auto-creates shapes, layouts, and connections from user instructions.
Installer - Click Below link to download drawio-ai-copilot:
👉 https://github.com/AI-Solutions-KK/drawio-ai-copilot/releases/latest
-
Based on draw.io desktop v29.3.6 with AI Copilot enhancements
-
AI Copilot for draw.io that draw any diagrams even most complex diagrams in 2 sec-
-
Diagrams — auto-creates shapes, layouts, and connections from user instructions.
Helps users quickly generate:
- flowcharts
- system architectures
- process maps
- agent workflows
- trees, and connected diagrams — without manual block placement.
This tool is designed for developers, architects, students, analysts, and product teams who want fast diagram creation from human-readable instructions.
AI Copilot needs an LLM API key to generate diagrams from natural language.
Steps:
-> AI-Copilot → Settings
-> Select your model provider
-> Paste your API key
Click Save
Generate diagram normally
No restart required.
Based on tested results and diagram quality:
✅ Preferred (Best diagram reasoning + structure):
Gemini - free
Claude - paid
Works fine for simple flows
May produce weaker structure for very complex architectures compared to Claude/Gemini as per individual experience
Claude → Anthropic Console
Gemini → Google AI Studio
GPT → OpenAI Platform
| Provider | Model | Dashboard Link |
|---|---|---|
| Gemini | aistudio.google.com | |
| Anthropic | Claude | console.anthropic.com |
| OpenAI | GPT-4o / GPT-3.5 | platform.openai.com |
- Dashboard: Google AI Studio
- Steps: 1. Sign in with your Google Account. 2. Click "Get API key" in the sidebar. 3. Click "Create API key in new project".
- Dashboard: Anthropic Console
- Steps: 1. Log in and navigate to the "API Keys" tab. 2. Click "Create Key". 3. Note: You typically need to buy at least $5 in credits to start using the API.
- Dashboard: OpenAI Platform
- Steps: 1. Log in to your developer account. 2. Click "+ Create new secret key". 3. Copy the key immediately; it will be hidden once you close the popup.
Describe what you want in plain English — Copilot generates connected diagram structures automatically.
Examples:
- User login flow with validation and error branch
- Microservice architecture with API gateway and database
- HR and IT agent routing workflow
No strict syntax required.
Copilot can generate:
- Flowcharts
- System architecture diagrams
- Agent workflows
- API & backend architecture
- Data pipelines
- Decision trees
- Control flow diagrams
- Service interaction maps
- Layered architecture
- Tool‑agent pipelines
- Validation flows
- Branching logic diagrams
Copilot adapts to request complexity.
Single Shape Mode examples:
- draw a circle
- create three rectangles
- add a database block
- draw five nodes not connected
Connected Flow Mode examples:
- Draw flow chart: start → process → decision → end
Copilot detects:
- steps
- decisions
- branches
- loops
- tools
- repositories
- databases
- routers
- agents
- pipelines
Generated diagrams are automatically:
- spaced properly
- non‑overlapping
- hierarchy aligned
- edge routed
- readable at scale
Supports multiple AI providers selectable in settings depending on quality, speed, or quota.
Step 1 — Open Copilot panel inside Draw.io.
Step 2 — Enter diagram description using natural language.
Step 3 — Click Generate Diagram.
Step 4 — Edit shapes manually if needed (all output is standard Draw.io objects).
Best pattern: short step‑style flow description instead of essays.
You can copy paste below prompt as it is & see the magic
* Draw a diamond Shape
* Draw three circles named A B C
* Make one decision node called Valid?
* Daw circle → square → diamond → database connect all
* Draw Login flow:
User logs in → validate → if valid dashboard → else error → end
* Draw Start node called User Start.
Then process Validate Input.
Then decision Is Input Valid.
If yes go to Save Data.
If no go to Show Error.
Both paths end at End node
Start from a UI / Web App / Corporate App where the user sends a message and later receives a response back.
Flow:
User message goes to a FastAPI chat endpoint.
From the endpoint, the message is sent to a Supervisor Router that controls routing and decisions.
The router also stores and fetches conversation context using a Memory Manager that connects to a Chat Repository and a Chat Sessions table database.
The Supervisor Router asks a decision question like “HR or IT request?” and performs intent classification.
From this decision, branch into two parallel agent paths:
Branch 1 — HR path:
Route to HR Agent.
HR Agent calls an HR Tool with parameters.
HR Tool writes data into Employee Repository.
Employee Repository stores into Employees Table database.
Results return back from HR Tool → HR Agent → LLM Client → Supervisor Router.
Branch 2 — IT path:
Route to IT Agent.
IT Agent calls an IT Tool with parameters.
IT Tool writes into IT Ticket Repository.
IT Ticket Repository stores into IT Tickets Table database.
Results return back from IT Tool → IT Agent → LLM Client → Supervisor Router.
Both HR Agent and IT Agent interact with a central LLM Client for reasoning and parameter parsing.
The LLM Client also receives past context from Chat Sessions storage.
Finally, Supervisor Router sends the final response back to FastAPI endpoint and then back to the UI app as user response.
Requirements:
- Show databases as database shapes
- Show agents and tools as process blocks
- Show router and LLM client clearly
- Show decision branching at router
- Show arrows for full round-trip flow
- Keep it as a connected architecture flow
Draw a layered GenAI architecture diagram with grouped sections and explicit connections.
GROUP: Application Startup
Framework Bootstrap -> Scan Documents Folder -> Knowledge Registry -> Ingestion Pipeline -> Vector Creation -> Vector Store
Knowledge Registry -> Ingestion Pipeline (only if new or changed)
Knowledge Registry -> Vector Store (if unchanged)
GROUP: Client / Developer Inputs
Company Documents -> Plugin Manager
Custom Functions -> Plugin Manager
Configuration YAML JSON -> Plugin Manager
GROUP: Core GenAI Framework
API Query -> Intent and Tool Router
Intent and Tool Router -> Plugin Manager
Plugin Manager -> Orchestration Engine (if plugin matched)
Plugin Manager -> Retrieval Layer (if no plugin)
Retrieval Layer -> Vector Store
Retrieval Layer -> Structured Database
Retrieval Layer -> Orchestration Engine
Orchestration Engine -> Session Memory
Orchestration Engine -> Company Context
Orchestration Engine -> Observability
Orchestration Engine -> Cost Policy Manager
Cost Policy Manager -> LLM Provider (allowed)
Cost Policy Manager -> Stop LLM Call (blocked)
LLM Provider -> Embedding Provider
GROUP: Execution Layer
External APIs -> Orchestration Engine
Orchestration Engine -> Standard Response
Standard Response -> Structured Database
Use:
- rectangles for services
- diamonds for decisions
- cylinders for databases
- grouped containers for each layer
- label decision edges: plugin matched / no plugin / allowed / blocked
- Use arrows or words like then, next, after
- Mention decisions explicitly
- Name components clearly
- Use yes/no branches
- Say “not connected” if no edges desired
- List architecture components and relationships
- Very complex diagrams need clearer step wording
- Dense graphs improve with ordered prompts
- No‑connection diagrams require explicit wording
- Software architecture design
- Backend flow mapping
- Agent systems
- AI pipelines
- DevOps flows
- Business processes
- Decision trees
- Data pipelines
- API maps
- Tool orchestration diagrams
- Natural language driven
- No rigid syntax
- Simple to enterprise diagrams
- Clean auto layout
- Fully editable output
- Multi‑model compatible
- Fast diagram bootstrapping
AI Copilot accelerates diagram creation. Generate fast, refine visually, deliver professionally.
Author & Copilot Developer
ML/AI- Professional - Mr. Karan Kamble
Tech Profile : https://github.com/AI-Solutions-KK
Linkedin Profile : https://www.linkedin.com/in/karan-tatyaso-kamble-b06762383/
FROM BASE REPO
drawio-desktop is a diagramming desktop app based on Electron that wraps the core draw.io editor.
Download built binaries from the releases section.
Can I use this app for free? Yes, under the apache 2.0 license. If you don't change the code and accept it is provided "as-is", you can use it for any purpose.
draw.io Desktop is designed to be completely isolated from the Internet, apart from the update process. This checks github.com at startup for a newer version and downloads it from an AWS S3 bucket owned by Github. All JavaScript files are self-contained, the Content Security Policy forbids running remotely loaded JavaScript.
No diagram data is ever sent externally, nor do we send any analytics about app usage externally. There is a Content Security Policy in place on the web part of the interface to ensure external transmission cannot happen, even by accident.
Security and isolating the app are the primarily objectives of draw.io desktop. If you ask for anything that involves external connections enabled in the app by default, the answer will be no.
Support is provided on a reasonable business constraints basis, but without anything contractually binding. All support is provided via this repo. There is no private ticketing support for non-paying users.
Purchasing draw.io for Confluence or Jira does not entitle you to commercial support for draw.io desktop.
draw.io is a git submodule of drawio-desktop. To get both you need to clone recursively:
git clone --recursive https://github.com/jgraph/drawio-desktop.git
To run this:
npm install(in the root directory of this repo)- [internal use only] export DRAWIO_ENV=dev if you want to develop/debug in dev mode.
npm startin the root directory of this repo runs the app. For debugging, usenpm start --enable-logging.
Note: If a symlink is used to refer to drawio repo (instead of the submodule), then symlink the node_modules directory inside drawio/src/main/webapp also.
To release:
- Update the draw.io sub-module and push the change. Add version tag before pushing to origin.
- Wait for the builds to complete (https://travis-ci.org/jgraph/drawio-desktop and https://ci.appveyor.com/project/davidjgraph/drawio-desktop)
- Go to https://github.com/jgraph/drawio-desktop/releases, edit the preview release.
- Download the windows exe and windows portable, sign them using
signtool sign /a /tr http://rfc3161timestamp.globalsign.com/advanced /td SHA256 c:/path/to/your/file.exe - Re-upload signed file as
draw.io-windows-installer-x.y.z.exeanddraw.io-windows-no-installer-x.y.z.exe - Add release notes
- Publish release
Note: In Windows release, when using both x64 and is32 as arch, the result is one big file with both archs. This is why we split them.
Local Storage and Session Storage is stored in the AppData folder:
- macOS:
~/Library/Application Support/draw.io - Windows:
C:\Users\<USER-NAME>\AppData\Roaming\draw.io\
draw.io is closed to contributions (unless a maintainer permits it, which is extremely rare).
The level of complexity of this project means that even simple changes can break a lot of other moving parts. The amount of testing required is far more than it first seems. If we were to receive a PR, we'd have to basically throw it away and write it how we want it to be implemented.
We are grateful for community involvement, bug reports, & feature requests. We do not wish to come off as anything but welcoming, however, we've made the decision to keep this project closed to contributions for the long term viability of the project.
PR TEST- AI-Copilot feature branch



