Introducing AutoCAD Bench

A 50-task benchmark for evaluating whether AI models can complete precise AutoCAD work using computer-use alone.

1.Presenting AutoCAD Bench

AutoCAD Bench tests whether multimodal agents can translate a dimensioned reference drawing into a correct, editable DWG. It is a fixed 50-task benchmark spanning 2D drafting and 3D reconstruction. Each agent receives a task prompt, a reference image, and a clean AutoCAD document and must work through visible mouse and keyboard actions.

2.The tasks

The benchmark covers complete 2D drafting and 3D reconstruction across four difficulty levels. It includes 21 2D and 29 3D tasks.

A basic 2D AutoCAD Bench reference showing a dimensioned stepped profile
2D basic: dimensioned profile
A project-level 2D AutoCAD Bench reference showing a detailed mechanical linkage
2D project: mechanical linkage
A basic 3D AutoCAD Bench reference showing a rounded bracket in isometric and orthographic views
3D basic: rounded bracket
A project-level 3D AutoCAD Bench reference showing a threaded and knurled part
3D project: threaded and knurled part

Task distribution

Difficulty2D3DTotal
Basic3710
Intermediate6612
Advanced6814
Project6814
Total212950

Expected output

2D: a complete Model Space drawing with correct geometry, dimensions, leaders, notes, center marks, and centerlines.

3D: true 3D Model Space geometry and a complete Layout1 sheet with every shown orthographic, isometric, section, and detail view and annotation.

3.The harness

Each turn observes one desktop state, emits an ordered action batch, and receives one fresh screenshot.

Diagram of the AutoCAD model harness showing task inputs, the model and available tools, its ordered action output, the AutoCAD environment, and screenshot feedback

Task

Task prompt
Reference
Agent
click
double_click
drag
move
scroll
key
type
wait
done

Current desktop frame

Fresh each turn

Output

Computer-use actions

01click(x, y)

02type("...")

03key("ENTER")

AutoCAD

Visible desktop

Validate

Execute

Capture frame

attempt.dwg
Fresh screenshot starts the next turn.

The loop ends when the model saves attempt.dwg and returns done.

4.The sandbox

Software
AutoCAD 2019 on Windows; one clean attempt.dwg is open at handoff.
Display
1920 × 1080, English locale, and a fixed versioned workspace.
Isolation
No shell, filesystem API, AutoLISP, automation API, MCP, external files, or desktop network access.
Artifacts
Final DWG, screenshots, model turns, and input events are retained for audit.

5.Scoring

Only the final attempt.dwg affects correctness. A trusted AutoCAD evaluator opens the file and extracts entity, geometry, dimension, annotation, extent, 3D, layout, and viewport evidence. It also produces a normalized render.

The judge compares the reference, gold render, candidate render, and checksum-bound CAD evidence. Equivalent native constructions are accepted; wrong scale, proportions, orientation, missing features, and extra geometry are not normalized away. Its task score is the benchmark ground truth.

ComponentWeightMeasures
Geometry60%Contours, features, scale, and proportions
Dimensions25%Values, symbols, completeness, and association
Annotations10%Leaders, notes, center marks, and callouts
Presentation5%Legibility, overlap, clipping, and drafting fidelity

raw score = 0.60 × geometry + 0.25 × dimensions + 0.10 × annotations + 0.05 × presentation

geometry gate = 35 + 0.65 × geometry

task score = min(raw score, geometry gate)

For benchmark reporting, a task counts as completed when its evaluator score is at least 75.

6.Results

Completion is the share of benchmark tasks with an evaluator score of at least 75.

01 · Overall

Task completion by model

Evaluator score ≥75 · 50 tasks

Sol
46.0%23/50
Terra
14.0%7/50
Fable 5
10.0%5/50
Luna
8.0%4/50
Opus 4.8
0.0%0/50
Kimi K2.5
0.0%0/50
Qwen3.7
0.0%0/50
Sol leads with 23 completed tasks.

02 · Modality

2D versus 3D

2D n=21 · 3D n=29

Sol
2D
66.7% · 14/21
3D
31.0% · 9/29
Terra
2D
23.8% · 5/21
3D
6.9% · 2/29
Fable 5
2D
4.8% · 1/21
3D
13.8% · 4/29
Luna
2D
19.0% · 4/21
3D
0.0% · 0/29
Opus 4.8
2D
0.0% · 0/21
3D
0.0% · 0/29
Kimi K2.5
2D
0.0% · 0/21
3D
0.0% · 0/29
Qwen3.7
2D
0.0% · 0/21
3D
0.0% · 0/29
Sol leads both modalities: 14/21 in 2D and 9/29 in 3D.

03 · Difficulty

Where capability holds

Completion rate

BasicIntermed.AdvancedProject
Sol
50.0%5/10
41.7%5/12
50.0%7/14
42.9%6/14
Terra
30.0%3/10
16.7%2/12
7.1%1/14
7.1%1/14
Luna
20.0%2/10
16.7%2/12
0.0%0/14
0.0%0/14
Fable 5
30.0%3/10
8.3%1/12
0.0%0/14
7.1%1/14
Opus 4.8
0.0%0/10
0.0%0/12
0.0%0/14
0.0%0/14
Kimi K2.5
0.0%0/10
0.0%0/12
0.0%0/14
0.0%0/14
Qwen3.7
0.0%0/10
0.0%0/12
0.0%0/14
0.0%0/14
Sol retains capability across every difficulty tier.

04 · Trace

Example of Sol successfully completing a task

ReferenceTask input
Dimensioned reference drawing for an AutoCAD task completed by Sol
Model viewStep 01 / 46
AutoCAD desktop observed by Sol at model turn 1

Actions emitted

Turn 1 · 1 action

  1. 01click(764, 998)

    Focus the AutoCAD command line for precise command entry.

7.Findings

The command line became the primary interface

Models overwhelmingly drove AutoCAD through typed commands and keyboard input. Mouse use was rare, and many clicks only restored command-line focus.

88.8%

typed commands or key presses

KeyboardMouse
Sol
5.2% mouse
Terra
7.2% mouse
Luna
8.8% mouse
Fable 5
14.6% mouse
Opus 4.8
18.3% mouse
641,347 direct interactions in the available traces across five runs. Wait and done actions are excluded.

Models act in bursts, then inspect

Long command sequences were often issued from a single screenshot. This suggests strong prediction of predictable AutoCAD state transitions, while also making a batch fragile when focus or dialog state diverges.

54.9%

of turns emitted multiple actions

90.2%

of actions occurred inside those batches

FRAME ttype(ARC)key(ENTER)type(x,y)key(ENTER)FRAME t+1

Average actions per model turn

Sol
11.0
Terra
8.6
Luna
7.3
Fable 5
4.9
Opus 4.8
2.1
The model sees one frame, commits to a batch, then sees the result—predicting intermediate UI states rather than observing each action.

The score rewards the result, not the construction

One drawback of the benchmark is that the current evaluator judges the saved output; it does not score the intermediate action trace or construction history. A visually convincing drawing can therefore hide semantically different CAD geometry.

Reference drawing for the mouse-shaped AutoCAD task
Target
Sol's submitted drawing for the mouse-shaped AutoCAD task
Sol submission
Overlay comparing Sol's submitted drawing with the target
Geometry overlay

Target construction

Radius-controlled arcs

Sol construction

One S-shaped spline

Final evaluator score

86.3 / 100

In this task, Sol matched the silhouette and every displayed value, but replaced the target's radius-controlled left arcs with an unverified spline. The evaluator noticed the mismatch, yet the strong visual and dimensional match kept the score above the completion threshold.

Recognizable form was not enough

Anthropic runs often recovered the broad shape before the drafting was complete. Fable produced recognizable forms but missed exact geometry, dimensions, centerlines, annotations, and layout details. Opus performed worse: only two tasks scored above 50, and none reached 75.

Fable 5Full coverage
Score ≥50
31/50
Score ≥75
5/50
Opus 4.8Full coverage
Score ≥50
2/50
Score ≥75
0/50
Score ≥50 reveals the distribution only; task completion remains fixed at 75.

8.Future Work

A stronger evaluator: pair visual scoring with entity semantics, geometric constraints, editability, and action-trace checks so visual similarity and CAD construction correctness are measured separately.

Extend the task set: the current benchmark contains only 50 tasks, which covers a fairly small distribution of real AutoCAD work. A larger, more varied set would provide a more representative measure of model capability.