Cizgen Docs

How it works

Understand how the Cizgen assistant reads your drawing, takes steps on its own, and checks its work before asking you to approve.

Cizgen doesn't just answer — it works in steps. For a single request it will read the drawing, measure, draw, look at the result, and correct itself, all on its own, until the task is done. You watch it happen and step in only when it asks or when it's time to approve.

The loop

  1. It reads first. Before drawing anything, Cizgen looks at your drawing to understand what's there. See Reading your drawing.
  2. It takes steps automatically. A request can take many steps — read, measure, draw, render, check — and Cizgen chains them without you driving each one.
  3. It sees its own results. After each step it reads the outcome (including images it renders) and decides what to do next.
  4. It stops to write. Anything that changes the drawing is held as a preview until you approve it. See The approval gate.

What you see while it runs

  • A live "Working…" line, often naming the current step (for example, Working · reading the drawing).
  • When it finishes, a "Worked for N steps" summary you can expand to see everything it did.
  • With some models, a short stream of the model's thinking as it reasons.

You can stop a run at any time with the stop button next to the prompt box.

A single request runs for as many steps as it needs, up to a safety limit. If a task is very large, break it into smaller requests — the conversation keeps full context between them.

Reading vs. changing

It helps to think of Cizgen's abilities in two groups:

  • Reading — looking, measuring, rendering, checking. These are safe and happen immediately; they never alter your drawing.
  • Changing — drawing, editing, placing blocks, deleting. These always go through a preview and are applied only when you approve.

This is why you can let Cizgen explore freely: it can't modify your drawing without your approval. The next pages cover each side in detail.

On this page