Canvas
Associative memoryEverything learned along the way, linked to what it relates to. Neither of you has to remember it.
Shared memory for you and your coding agent
Claude Code reads your diagrams before it touches the repo, and writes back what it learned and what is left. You watch the canvas change while it works.
What the agent learned is written to a diagram, not lost in a scrollback. The next session starts by reading it.
Every note and task it writes lands on the canvas as it happens. A graph you read at a glance, not a log you parse.
Diagrams only, files inside one folder, or commands too. The program enforces it, not the window.
Five modes
Not five diagram types: five ways a project remembers. You and Claude read and write all of them.
Everything learned along the way, linked to what it relates to. Neither of you has to remember it.
Agents, the folders each one may touch, and what each one is allowed to run. Drawn, so you can check it.
The map of what exists and why it was decided that way.
What is left, in order, with what depends on what.
The data model as classes and objects. The same graph fires the HTTP requests that test it.
There are two more — a study questionnaire and a document library. They are in there; they are just not the point.
Get it running
This page already works in your browser. For Claude to read and write your diagrams, something has to run on your machine. Pick one.
You are already in the app. What is left is telling Claude where to find it.
One file. The app and its backend, together.
Rather run it from source with Python? The repo explains how.
Its own window. It tells you when there is a new version.
Windows: double-click it.
macOS: unzip it and move the app to Applications. It is not signed yet, so the first time macOS warns you: right-click it → Open, or System Settings → Privacy & Security → Open Anyway.
Linux: chmod +x DiagraMinder-linux && ./DiagraMinder-linux
Your projects live outside the program, so updating never touches them.
./DiagraMinder-linuxPaste the .mcp.json at your project root, then run /mcp.
In the app: Settings → This program. Copy the .mcp.json it shows — address and password already filled in — and paste it at the root of your project.
In Claude Code, run /mcp: it should show diagraminder connected. Ask it to read your diagrams before it touches the code.
/mcpEnforced by the program, not the window.
Same screen, What the MCP can do: diagrams only (the default), diagrams + files inside one folder you pick, or also commands.
One switch opens a Cloudflare tunnel to the app.
Reach it from Claude web opens a Cloudflare tunnel (it needs cloudflared; the app tells you how to install it). Add the address it gives you as a custom connector in Claude web: it asks for the password once. The tunnel dies when you turn it off or close the app.
cloudflaredA download, or one Python command. No dependencies.
From source: clone the repo and run python3 backend/server.py. The code is open: read it before you run it.
Settings → Connect backend, with the password it printed.
Here: Settings → Connect backend. The first time it asks for a password: the backend prints it when it starts, and keeps it in token.txt inside its data folder.
token.txtPick Local · Claude Code, or any agent CLI you have installed.
Open the chat and pick Local · Claude Code — or any agent CLI you already have installed. It runs on your own subscription, and it can read and edit the project you choose.
The backend panel has the .mcp.json and the MCP permissions.
The backend's panel (http://127.0.0.1:8765/panel) shows the .mcp.json under MCP. Paste it at the root of your project and run /mcp in Claude Code. The same panel sets what the MCP may do.
127.0.0.1:8765/panelThe same panel opens a Cloudflare tunnel.
From the same panel, the Cloudflare tunnel gives you an address to add as a custom connector in Claude web. It needs cloudflared and asks for the password once.
cloudflaredPaste the .mcp.json at your project root, then run /mcp.
Settings → This program. Copy the .mcp.json it shows — address and password already filled in — and paste it at the root of your project.
In Claude Code, run /mcp: it should show diagraminder connected. Ask it to read your diagrams before it touches the code.
/mcpEnforced by the program, not the window.
Same screen, What the MCP can do: diagrams only (the default), diagrams + files inside one folder you pick, or also commands.
One switch opens a Cloudflare tunnel to the app.
Reach it from Claude web opens a Cloudflare tunnel (it needs cloudflared; the app tells you how to install it). Add the address it gives you as a custom connector in Claude web: it asks for the password once. The tunnel dies when you turn it off or close the app.
cloudflaredRuns on your machine
The app and its backend run locally. The Claude web tunnel only exists while you keep it on. The backend's code is public, so you can read it first.
Read the backend sourceProjects are plain files in folders you choose. Updating the app never touches them.
Nothing to sign up for, nothing to sign in to.
Use your own subscription or keys. The canvas works without any AI at all.
Yours or the agent's: anything written to a diagram can be undone.