Approvals
How the preview-and-approve gate works when Cizgen runs inside Claude Desktop, Claude Code, Cursor, or VS Code.
Cizgen MCP keeps the same safety model as the panel: nothing is written to your drawing without your approval. Every draw, edit, or delete is first staged as a preview in AutoCAD, and it becomes permanent only after you approve it. The approval gate concept is identical — what changes in MCP is where the question reaches you.
Where you approve
The preview appears in AutoCAD
When the AI finishes staging a change, the pending geometry is visible on your canvas — you can pan, zoom, and inspect it before deciding.
The approval question appears in your chat
In hosts that support in-chat prompts (Claude Desktop and Claude Code today), a dialog opens right in the conversation with a short summary of what will change — for example 3 entities drawn, 2 blocks placed — and Approve / Reject choices.
In hosts without in-chat prompts, Cizgen falls back to AutoCAD itself: AutoCAD comes to the foreground and the command line asks you to choose Approve or Reject.
Your decision is applied
- Approve — the change is committed and becomes a normal part of the drawing (AutoCAD's
own
UNDOcan take it back). - Reject — the preview is discarded and the conversation continues, so you can refine your request.
Closing the dialog is not a rejection
Only an explicit Reject discards staged work. If you close the approval dialog without deciding, press Esc, or let it time out, the preview stays in AutoCAD and the AI is told the decision is still pending — it can ask again, or you can tell it to commit or discard. This protects work the AI spent real effort preparing from being lost by an accidental click.
The AI cannot approve itself
Approval is enforced with a cryptographic permission that is issued only after a human approves — the model never sees or handles it. A misbehaving or confused AI cannot commit a change on its own, no matter what it sends; the plugin refuses anything that didn't go through your approval.
If the AI's self-check found geometry problems and it asks to commit anyway, the approval summary says so explicitly (for example "ERROR-level findings will be bypassed") — you are never approving an override without knowing.