Build CAD tools with AI, run on Leaf
What should Leaf do to your project?
Mounted onthe Claude family — Sonnet 5, Opus 4.8, Haiku 4.5, Fable 5 — or your own Claude account.
- Sonnet 5
- Opus 4.8
- Haiku 4.5
- Fable 5
- your own Claude account
Leaf runs AutoCAD work in the cloud today, inside the rules you set: one prompt, two lanes — Run · Build. You confirm before anything runs — paid actions never auto-execute.
Type what you want, and Leaf Automation Studio authors a real CAD tool you keep: run it in the Studio, then export it to AutoCAD. That authoring-and-export path is what we are building now.
Every line above is graded below, with the evidence in the release room.
Would build a tag-combiners tool, run it here, then export it to AutoCAD. The export step is not shipped yet.
- Where this is today
- Evidence for each line is in the release room below.
- Runs in the cloud
- liveCanonical worker on the production spine.
- Operates in the drawing
- liveConsole submit reaches the run lane. Gate G1 is open.
- Mount your Claude account
- in buildControl is shipped but dormant; the session-model route is not live.
- Tools you export to AutoCAD
- in buildTool authoring runs ahead of the export path.
Release room
Loading confirmed status
Waiting for the first confirmed release snapshot.
- State
- Pending
- Environment
- Unconfirmed
- Confidence
- Unconfirmed
- Evidence updated
- Waiting
Milestone board
Blockers and decisions
Evidence and change log
Public evidence only. No names, files, prompts, account identifiers, customer identifiers, or secrets.
The full product
What full launch means
Leaf Automation Studio is intended to give a CAD user one place to run a tool, solve a constrained drawing problem, or define a reusable drafting task. Type what you need; the Studio authors the tool. Run on Leaf or export to AutoCAD. The product should keep the machinery out of the way while making each result easy to review.
Run
Use an available CAD tool on the drawing in front of you.
Choose a drafting task such as counting, measuring, routing, stringing, tagging, or changing drawing objects. At full launch, the Studio should show which tool is available before you run it.
Solve
Set the rules for a constrained drawing problem.
Ask for a result that follows your stated limits, then inspect and revise that result. The engineer keeps control of the engineering decisions.
Build
Define a repeatable drafting task that needs its own tool.
The goal is a reusable company tool with a clear review step. At full launch, an approved tool should handle later runs without recreating the task each time.
Trust
Review what ran and what changed in the drawing.
A useful result should identify the drawing version, tool, rules, and access that produced it. That record gives a reviewer the context needed to accept or reject the work.
Plain English
What the jargon means
These terms describe how the product is built. They should not make it harder to understand.
- Capability registry
- The current list of tasks the Studio is allowed and able to do.
- Canonical worker
- The approved computer assigned to perform a job.
- Provenance
- A record of the drawing, tool, rules, and machine behind a result.
- Tenant isolation
- The separation that keeps one company's drawings, tools, and access apart from another company's data.
- Deterministic tool
- A tool designed to handle the same approved input in the same defined way each time.
See the product surface
Open the Studio to see the current product. Return to this page for release status and the evidence behind it.
Open the Studio