NativeCAD Pinpoint · new in 0.30.0 · By FeatureBoard Labs

Pinpoint: see what your AI agent changed in every CAD version

The quadcopter's rotor wake in hover, from a solver run in the same project. How the solver results get here

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.

Version ·
Loading the quadcopter…
Click a part to name it.

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.

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.

Pinpoint’s Solvers panel listing the quadcopter’s rotor runs: run name, rpm, speed, thrust, power and whether it settled, with Charts and Wake buttons on the selected run and a warning that it has not settled.
The Solvers panel on the quadcopter project.

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.

Hover, 5,427 rpm.
6 m/s, 5.4 degrees nose down.
15 m/s, 23.0 degrees nose down. The wake streams back.

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.

The controls under an animated Pinpoint window with the video export’s options open: picture size, number of loops, MP4 or WebM, a tick box for the caption and scale, Save and Cancel.
The video export's options under the window.

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/srpm, front / rearNose down, °Power, WPack, AForce left over
05,427 / 5,4270.068.64.50.6 %
64,771 / 5,4275.451.93.50.2 %
104,865 / 5,40910.654.83.70.2 %
155,477 / 5,92723.085.55.51.2 %
207,373 / 7,67339.0164.610.30.8 %
259,995 / 10,13053.8300.119.21.1 %
3012,677 / 12,75062.0520.336.51.4 %
0100200300400500600010203040506070051015202530speed, m/s power, W (left)nose down, degrees (right)
Power is lowest near 6 m/s and climbs steeply after 15.

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 %.

One rotor of the hovering quadcopter with its wake at the ordinary resolution: broad, smooth tubes.
Ordinary, 20 cells per rotor radius.
The same rotor from the same camera with the refined wake: thin, separate vortex tubes winding down under the rotor.
Refined: 40 cells per rotor radius inside the box. One rotor's wake shown.

Driving the solver from a chat

The solver is one tool, cad_wind_tunnel:

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.

PartsNo.ProcessMaterialRule packChecksPassedFlagged
Frame plates2Waterjet-cut sheetCarbon fibreWaterjet sheet rules, with a sheet-cutting service's published design guidance for carbon fibre1064
Arms4Waterjet-cut sheetCarbon fibreWaterjet sheet rules, with a sheet-cutting service's published design guidance for carbon fibre1688
Prop spacers4Turned from barAluminiumturning20200
Legs, leg mounts and wire covers12Fused-filament print, 0.4 mm nozzleTPUfdm24240

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.

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.

Pinpoint’s Manufacturing panel on the quadcopter project: a line for the checks and one for the parts list, then a table of parts with class, rule pack and checks, the plates and arms flagged and the spacers passing.
The quadcopter's parts with their rule packs and checks.
The bottom plate opened in the Manufacturing panel: how it is made, then each check with pass or flag and what was measured and what it was held to, and its row of the parts list.
The bottom plate opened: each check with what was measured.

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:

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.

      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
      OpWhat it does
      start, openAttach to this machine's Pinpoint or start it, and give the address of the hub, a project or one window.
      projectA new project. It is refused without its prompt; the prompt and requirements become its first goals.
      importA CAD or mesh file as a new version, with its parts named and grouped from a manifest before it lands.
      goals, seed, goal, goal-stateRead the goal tree, seed it, add or edit a goal, and set a goal met, open or dropped with evidence.
      pin, pins, resolve, checkPin on a part, list pins, close one, and pin a check's result, which can also mark a goal met or open.
      versions, historyEach window's versions and what each changed, and the record of goals and pins.
      inboxTake 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 →

      Build your own part with NativeCAD

      Try it free with the keyless evaluation · $200 per seat per year · Kernel SDK for products.