SpecMode
Coming early ’27
Draw the system.
Let the agents build it.
DrawMode today is a place to think. Where we're taking it is bigger: the shared model between you, your AI tools and your code — the description a system is built from, reflecting the reality of what it is, in powerful ways. Not the picture drawn after.
DrawMode is the base for SpecMode — where a human doesn't just draw the system but describes, constrains and specifies it, setting the guard rails the agents build within. And the mirror works both ways: SpecMode reflects diagrams back showing how the system actually works, so your mental model and your AI assistant's are the same picture.
SpecMode in the loop: the team constrains and specifies, the agents build, and the understanding flows back.
A spec agents can build from
A DrawMode diagram is a real model — types, relationships, constraints. That makes it precise enough for an agentic coding assistant to implement, and human enough for your team to argue over first. Agree on the drawing; hand it to the agent; get software.
AI that draws its thinking
When an agent proposes a change, it shouldn't hand you four thousand lines of diff. It should hand you a diagram — its mental model of your system, and exactly what it intends to do to it. You review a picture you can disagree with.
See what your agents build
Agentic assistants produce a lot of code, fast. DrawMode keeps a live architecture view over your local codebase — so you can see the system they're actually creating, and catch the drift the day it starts, not the quarter after.
The plumbing is MCP
DrawMode is growing a Model Context Protocol server: tools any agentic assistant can call to read your models, write them, and publish architecture views of your local codebase. Claude Code or whatever you run — if it speaks MCP, it can draw with you.
Start where the loop starts.
Draw the system you mean to build — the rest of the loop is coming to meet you.