Pinpoint: see what your AI agent changed in every CAD version
Keep one page open and watch your AI agent design. Pinpoint shows every model it is working on, what changed in each version, the goals you set, every check pinned on the part it is about, and the solver runs made on it. Below is a real project, a 200-part quadcopter: step between its two versions, watch its rotor wake, open its pins.
Drag to orbit, scroll or pinch to zoom. The numbered dots are the project's pins, shown on the version they were made on. The group buttons hide and show the 7 groups.
What the agent changed, and why
Version 1 is the original layout: 196 parts. Version 2 re-laid the quadcopter so the rotor CFD could run on it as built. That method needs plain fluid in a ring around each prop, so nothing but the prop's own spinning parts may sit within 146 mm of a motor axis at prop height.
- The props were raised 34 mm on four new aluminium spacers, with longer shafts to match.
- The battery became a 6S1P Li-ion 18650 pack, 66 × 38 × 38 mm, centred. It was a 110 × 40 × 30 mm LiPo. The strap slots in the top plate follow its width.
- The GPS moved onto a mast at x +42 mm with a 24 mm puck, the video antenna stands straight up through the top plate, and the battery leads run low.
In Changes, version 1's parts that differ are orange and version 2's are blue: 35 parts changed, 4 were added and 0 removed. The other 161 are the same and drawn as a ghost. The page downloads version 2 whole and only the version 1 parts that differ, 1.3 MB in all, which is how Pinpoint opens a window.
Its flow, in the same project
The quadcopter's flow runs are in the project beside its model. In Pinpoint's Solvers panel each run is a row: rotor speed, flight speed, total thrust, power, and whether every rotor settled. The selected run shows its set-up above the list, and says whether it has settled. Charts plots each rotor's thrust per revolution and its power. Wake opens the flow itself as a model you can orbit and play.
The wake, frame by frame
Each clip loops the wake: one rotor revolution in hover, half a revolution in forward flight, where the two-bladed props look the same again. The surface marks where the flow swirls; its colour is flow speed as a share of the rotor tip speed, on one scale for every frame.
An animated window has a frame slider and a speed choice. From release 0.35.0, Export saves it as a video, as numbered pictures, or as one 3-D file holding every frame. The clips on this page were saved that way.
Level flight, from hover to 30 m/s
At each speed the trim sets the front pair's rpm, the rear pair's rpm and the pitch until lift balances the 948 g weight with no net force along the flight path and no pitching moment; the last column is the force left over, as a share of the weight. The rear pair ends up faster: about 14 % at 6 m/s, 1 % at 30.
| m/s | rpm, front / rear | Nose down, ° | Power, W | Pack, A | Force left over |
|---|---|---|---|---|---|
| 0 | 5,427 / 5,427 | 0.0 | 68.6 | 4.5 | 0.6 % |
| 6 | 4,771 / 5,427 | 5.4 | 51.9 | 3.5 | 0.2 % |
| 10 | 4,865 / 5,409 | 10.6 | 54.8 | 3.7 | 0.2 % |
| 15 | 5,477 / 5,927 | 23.0 | 85.5 | 5.5 | 1.2 % |
| 20 | 7,373 / 7,673 | 39.0 | 164.6 | 10.3 | 0.8 % |
| 25 | 9,995 / 10,130 | 53.8 | 300.1 | 19.2 | 1.1 % |
| 30 | 12,677 / 12,750 | 62.0 | 520.3 | 36.5 | 1.4 % |
What ends it is the battery this design specifies: a 6S1P pack rated at 35 A continuous, which the trim reaches at about 29.6 m/s. At 30 m/s the rotors turn at 12,677 / 12,750 rpm, a tip Mach number of 0.47, with the nose 62.0 degrees down.
A finer grid around the rotors
rotorRefine (release 0.35.0) puts a finer grid in a box around each rotor and its near wake: here 20 cells per rotor radius outside and 40 inside. On a single reference propeller the patched run reads thrust within 0.3 % and the size of the tip-vortex core within 1.4 % of a run that is fine everywhere, with 38 % of the cells. Without the patch the cores come out 1.9 times as wide. On the quadcopter in hover it is 10.9 million cells against 44 million, with each rotor's thrust within 0.7 %.
Driving the solver from a chat
The solver is one tool, cad_wind_tunnel:
mode: "transient"withrotorMethod: "actuatorLine"or"actuatorDisc": each rotor given as its propeller body and an rpm, its loads worked out from each blade's own sections at about 20 cells per rotor radius.rotorRefine: {ratio: 2}: the finer grid around each rotor.cutCells: true: steady drag on cut cells. A 40 mm cube reads a drag coefficient of 1.04 with it and 1.26 without, against a published 1.05.cad_help({topic: "quadcopter"}): a worked multirotor run with the trim recipe.
The runs on this page were recorded by NativeCAD's command-line runners, which write a run into a project as it solves. From the chat, cad_pinpoint pins a run's numbers on the part they are about and brings a result file in as a model.
How it is made, checked in the same project
The design says how each part it makes is made. The plates and arms are carbon fibre, cut from sheet by waterjet. The prop spacers are aluminium, turned from bar. The legs, leg mounts and wire covers are printed in TPU. Each of those 22 parts was run through NativeCAD's rule pack for its process: 70 checks, of which 58 passed and 12 were flagged, on six parts. The six frame standoffs are bought, each an M3 × 30 mm aluminium hex standoff, and are not checked.
| Parts | No. | Process | Material | Rule pack | Checks | Passed | Flagged |
|---|---|---|---|---|---|---|---|
| Frame plates | 2 | Waterjet-cut sheet | Carbon fibre | Waterjet sheet rules, with a sheet-cutting service's published design guidance for carbon fibre | 10 | 6 | 4 |
| Arms | 4 | Waterjet-cut sheet | Carbon fibre | Waterjet sheet rules, with a sheet-cutting service's published design guidance for carbon fibre | 16 | 8 | 8 |
| Prop spacers | 4 | Turned from bar | Aluminium | turning | 20 | 20 | 0 |
| Legs, leg mounts and wire covers | 12 | Fused-filament print, 0.4 mm nozzle | TPU | fdm | 24 | 24 | 0 |
The carbon-fibre numbers are a sheet-cutting service's own, read from its published pages on 2026-11-17. Its design guidance recommends a hole of at least 3.18 mm and a web between cuts of at least twice the sheet thickness. The waterjet leaves an inside corner no sharper than 0.81 mm, and the sheet comes 1.02, 1.6, 2, 3, 4, 5 or 8 mm thick. The spacers and the printed parts passed every check; every flag is on the carbon parts.
What was flagged
Press a part to see the flag on the model at the top.
- Minimum web between cuts. Thinnest web 1.4 mm; the guide recommends at least 6 mm, twice the sheet thickness.On
- Minimum internal corner radius. 8 inside corners drawn sharp; the cut leaves a 0.81 mm radius there.On
- Minimum web between cuts. Thinnest web 3.41 mm; the guide recommends at least 4 mm, twice the sheet thickness.On
- Minimum hole diameter. 2 holes of 2.2 mm; the guide recommends at least 3.18 mm.On
- Minimum web between cuts. Thinnest web 3.4 mm; the guide recommends at least 12 mm, twice the sheet thickness.On
- Listed sheet thickness. 6 mm is not a sheet the service lists; the nearest are 5 and 8 mm.On
In Pinpoint's Manufacturing panel
The same record is a panel in the project. Every part is a row with its process and its checks, and a part opens to each check with what was measured and what it was held to. The panel reads the records a project writes: checks, parts lists, print plates and ply books. It is in the release 0.36.0 download, with print plates and parts lists.
Asking for the checks from a chat
The checks are one tool, cad_dfm_check, called on a part with the name of a rule pack:
- A sheet-cutting rule pack with
params: {materialThickness: 3}for the bottom plate. A shop's own number, a hard minimum or a recommended one, goes inrules, asmin_hole_diameter: {limit: 3.175}does here. process: "turning"for a turned part, andprocess: "fdm"withparams: {buildDirection: [0, 0, 1]}for a printed one.- Each rule comes back passed or failed with what was measured and its limit, and a failed rule names the faces it failed on.
The record on this page was written by a script that runs those rule packs over the 22 parts and compares each sheet's thickness with the thicknesses the service lists. From the chat, cad_pinpoint's check pins a failed rule on its part as a defect.
The project's record: pins and goals
A check is pinned on the part it is about, and a goal carries its evidence. These are the project's own, copied as written.
Pins (8)
Each pin is on a part, at a point in model millimetres. Click one to read it; the model at the top turns to its version and part. A row the AI wrote is signed "Claude (co-author: person)".
Goals (12 of 12 met)
The prompt the project started from is the first goal, with its requirements under it. Open a row for its evidence.
What Pinpoint does
Pinpoint runs on your own machine at http://127.0.0.1:8790/ and reads the files NativeCAD already writes: MCP session journals, viewer packs and solver results. Nothing has to opt in. Every project gets a section, every document or pack a window, and every change a version.
- Windows. Each shows A, the previous version, in orange over B, the current one, in blue, with unchanged parts ghosted. Back, Next and Live step through the versions it holds. History lists them with what each changed, and any two can be compared.
- Look. Changes, Solid, Solid with lines, Hidden line, Wireframe and a drawing sheet, plus Textured, Zebra and X-ray when the project has its own viewer.
- Results by kind. CFD and FEA runs are grouped by the kind of analysis, each with its own columns and charts, as the rotor runs above are.
- Manufacturing. A project's checks, parts lists, print plates and ply books in one panel, as the quadcopter's above are.
- Folding. A project with many models folds each window to a card that holds no model and no WebGL context until it is opened again.
- Goals. A project starts from its prompt and requirements, recorded as its first goals. Goals form a tree, each with a state and the evidence for it.
- Pins. Click a model to pin a note, question, enhancement or defect on a part. A check pins its result on the part it is about, and a failed check is a defect. A defect closes only through a passing check on a newer version. Where a version records its B-rep faces, a pin is linked to the face, and Pinpoint reports when that face changes or goes.
Drive it from any chat
One tool, cad_pinpoint, puts Pinpoint in every NativeCAD chat. Your assistant can start Pinpoint, record the prompt, bring a model in with every part named and grouped, and pin each check's result on its part. Goals and pins written this way are signed "Claude (co-author: person)". The pins on this page were written that way.
The tool's ops
| Op | What it does |
|---|---|
start, open | Attach to this machine's Pinpoint or start it, and give the address of the hub, a project or one window. |
project | A new project. It is refused without its prompt; the prompt and requirements become its first goals. |
import | A CAD or mesh file as a new version, with its parts named and grouped from a manifest before it lands. |
goals, seed, goal, goal-state | Read the goal tree, seed it, add or edit a goal, and set a goal met, open or dropped with evidence. |
pin, pins, resolve, check | Pin on a part, list pins, close one, and pin a check's result, which can also mark a goal met or open. |
versions, history | Each window's versions and what each changed, and the record of goals and pins. |
inbox | Take the pins aimed at this machine by another member of the team. |
Pins and goals also travel between the machines of a team, over the team's encrypted link. Everyone on the team sees the same open defects and the same goals: see NativeCAD Teams.
About this replay
The model is rebuilt from the quadcopter's design file as it stood before and after the change, with NativeCAD's own operations, and tessellated for the screen at 0.2 mm. The goals and pins are the project's own record, copied as written, with times in UTC and internal ticket numbers shown as [ticket]. Live updates, the Solvers panel and writing pins need Pinpoint running on your machine; the pins were saved without a camera, so clicking one turns to its point from the current view.
Build your own part with NativeCAD
Try it free with the keyless evaluation · $200 per seat per year · Kernel SDK for products.
More demos
All demos →A deathmatch game that runs on checked CAD data
A browser deathmatch on a map of B-rep solids, proven sealed by a gate and worked issue by issue in Pinpoint.
20 checks pinned in Pinpoint Arena: Vanguard modeA shield arena on four maps drawn as CAD solids
Shields, vehicles and capture the flag on four maps of our own, each proven by a gate and pinned in Pinpoint.
64 checks pinned in Pinpoint FEA loopFinite-element analysis your agent can run
Stress and vibration results from the same AI session that built the part, with the peak and its margin.
6 designs solved in FEA Drawings to STEPManufacturing drawings in, STEP out, checked against the original
Real manufacturing drawings become exact 3D models, each matched against the official model.
6 of 6 NIST parts matchedBuild your own part with NativeCAD
Try it free with the keyless evaluation · $200 per seat per year · Kernel SDK for products.