Things we wrote down while building Forgent3D: OpenSCAD details, the road to running a CAD kernel in the browser, and what a few thousand real .scad files taught us. Updated when there is something to say.
Seeing what a piece of OpenSCAD code looks like does not require installing OpenSCAD. Paste it into a viewer in the browser, it renders when you pause, colours match the desktop, and the code can go into a link for someone else.
When the agent makes a box, ten times out of ten it needs insert bosses on the base and a catch on the lid, and it derives the numbers from scratch each time. One wrong number is one failed print. So we made the most common 3D-print joints into a library.
The walls of a hole come out green and that is not a mistake. The preview's colour conventions, why the outer color() wins, and what happens to % and # in preview and render.
OpenSCAD only exports meshes like STL, so getting a STEP file takes a detour. The FreeCAD workbench, mesh-to-STEP converters, remodelling by hand, each with its own cost. Which road fits which job, and an online converter that needs no install.
Eight experiment cells to answer "was that prompt better". No answer came back. What did: rerunning one configuration swings it by 16 points, while every difference we wanted to measure is under 10.
A language model cannot see in 3D; it only knows the code ran. We give it feedback it can read, a dimension report, orthographic views, throwaway probes, a knob test. What each one answers.
There are two ways to do AI CAD, a mesh from a sentence or parametric code from a language model. We took the second, and this is why, and what it costs.