1DesignToolDownload

Agents · since v1.0.0

Your coding agent is the designer

Claude Code, Codex, Cursor Agent, Gemini, Devin and eleven more — whichever CLI you trust, 1DesignTool drives it as a designer and holds its output to the same visual bar.

DownloadRead the docs

Why it matters

Design tools ship their own models and your taste pays the bill when the model's taste runs out. Your coding agent already knows your stack and your conventions; the studio gives it a design vocabulary (the kit), a stage to render on (the preview) and a referee (the gate) so 'the agent made a page' becomes 'the agent made a good page'.

How it works

  1. 1Pick any installed agentThe Agents settings panel lists the CLIs it found on your machine. Each gets the same contract: files in, transcript out, gate verdict back.
  2. 2One loop for all of themBrief → build → gate → steer is identical across agents. Swap the driver mid-project and the history, preview and kit don't notice.
  3. 3Per-project model and effortEach project remembers which agent, model and effort level drove it, and which permissions it ran under.
  4. 4Compare their workVariants let different agents answer the same brief — then you judge the results blind, without knowing which CLI made which.

Capabilities

  • 16 supported CLIs, each with a definition and transcript parser in the bridge
  • Headless subprocess contract: the app owns spawn, stdin, stop and exit codes
  • Same design kit, preview and gate regardless of which agent drives
  • Per-project agent, model, effort and permission settings
  • Usage and token tracking per agent per turn

Without it

Bet on one AI design tool's in-house model, export SVGs, and start over when it can't read your codebase.

With 1DesignTool

Keep your agents. The studio makes each of them a better designer, and lets them compete on the same brief.

FAQ

Which agents are supported?

Claude Code, Codex, Cursor Agent, Gemini CLI, Devin, Aider, Amp, Grok, Kimi, Kiro, OpenCode, Cline, Hermes, Pi and Qwen — sixteen CLIs, each with its own bridge definition and parser.

Do I pay 1DesignTool for the AI usage?

No. The agent runs on your accounts and your quota — the studio tracks cost per turn so you can see it, but billing stays between you and the agent provider.

Can different agents work on the same project?

Yes. The project keeps its files, history and kit; the driving agent is a per-turn choice, so switching mid-project is normal.

What if my agent isn't on the list?

The bridge is open: a CLI needs a definition file and a transcript parser. The docs walk the shape of both.

In the docs

Related features

AgentsClaude Code design toolPoint 1DesignTool at your Claude Code install and it becomes your designer — writing HTML, CSS and JS into a project folder you own, with a live preview and a design check before anything counts.Read more →SteeringA design kit the agent has to passThe gate is the difference between 'generated' and 'shipped': kit checks run on every turn, and in Reviewed or Council mode independent critics judge the frozen evidence before the result counts.Read more →CodebaseVisual editor for your real codebaseBuild mode is a visual editor for the code you ship: pick an element in your running app, edit it visually, and the change lands in the component's own idiom — verified by a real re-render before it's yours.Read more →

Design with the agent you already have.

Free to try, buy once — the studio and your own coding CLIs do the rest.

Download