open source · MIT · version 0.2.0

Diagrams of software that an agent draws in seconds.

Ask your agent to show what it built, what it is building, or what it plans. It writes a few lines of text, and swe-diagrams turns them into a diagram. Each part can show a status: done, in progress, planned, added, changed, or removed.

Get it Watch the demo

Install in one step. Paste this into Claude Code, Codex, Cursor, or another coding agent. It installs the program and the skill, and draws a test diagram.

Show me how

How to get it

Pick one way. Each gives you the swe-diagrams program. The agent skill tells your agent when and how to use it.

easiest

Give it to your agent

Paste this into your coding agent. It follows the install steps and draws a test diagram.

Install swe-diagrams for me. Follow the steps in https://github.com/Benny-Gil/swe-diagrams/blob/main/docs/install.md
Claude Code

Plugin

Gives Claude Code the skill. It also needs the program: use one of the next ways.

/plugin install swe-diagrams --marketplace Benny-Gil/swe-diagrams
macOS · Linux

Install script

Puts the program in ~/.local/bin and the skill in ~/.claude/skills.

curl -fsSL https://raw.githubusercontent.com/Benny-Gil/swe-diagrams/main/install.sh | sh
all systems

npm

A small launcher. The first run downloads the release binary and checks it against SHA256SUMS.

npx swe-diagrams render app.sd -o app.svg
all systems

Cargo

Builds the program from crates.io. Then copy skills/swe-diagrams into the skills folder of your agent.

cargo install swe-diagrams
no tools needed

Prebuilt binaries

Each release has binaries for macOS, Linux, and Windows, and a SHA256SUMS file.

Then ask your agent: “Draw the architecture of this repo.” or “Make a plan diagram for this change, and update it as you work.”

What it draws

Every picture comes from a few lines of text. The program places everything, so the agent never looks at the picture to fix it. One diagram takes about 3 milliseconds. Pictures follow your light or dark setting.

Architecture diagram of a checkout service with the status of each part
Architecture. Which parts exist, which one the agent works on, and which are planned.
Plan graph for a rate limit feature
Plan. The order of the tasks, and where the work is now.
Sequence diagram of a login
Sequence. The calls of one request, with a status on each message.
User journey through the pages of a checkout
Journey. Pages as small browser frames, and user actions on the edges.
Entity relationship diagram of tables
Entities. Tables, keys, and a status on each field.
State machine of an order
State. States, events, and the start and end marks.

Twelve types in all: architecture, sequence, plan, dependencies, flow, state, data flow, change map, entities, classes, timeline, and journey. Output goes to SVG, an interactive HTML page, PNG, GIF, MP4, and terminal text. A node can open a detail level, and a story can play the motion of a request.