// the take
A LangGraph-orchestrated pipeline that turns a natural-language brief into actual parametric CAD (via build123d/OpenCascade), executing and repairing the generated Python until it passes geometric and visual QA, then exporting STEP/STL/GLB (and URDF for multi-part assemblies). Aimed at mechanical engineers or roboticists who want editable geometry from a prompt rather than a one-shot render, and who are comfortable running an agent pipeline locally against an LLM API.
Generation isn't one-shot: there's an execute-check-repair loop plus an independent Judge and visual verification, and the single-part benchmark (140/141 features passing) backs that up with real numbers rather than vibes. Outputs are genuinely editable engineering artifacts (STEP/STL/GLB, URDF), not images, and repeated/mirrored components get reused instead of regenerated, which is a real cost and consistency win. The web UI has had actual security attention — CSRF header requirement on mutating endpoints, an explicit provider/host allowlist, path-traversal guards on artifact copy, and a documented (if leaky) env-var allowlist for the subprocess that runs generated code.
Install is fragile: it's pinned to OCP 7.x / build123d <0.13, and aider-chat's numpy 1.x pin directly conflicts with build123d's numpy 2.x requirement, so you're stuck doing --no-deps / force-reinstall gymnastics that will quietly break on any version bump. The multi-part assembly workflow — the headline feature in the gallery — is explicitly labeled a 'technology preview' with curated examples and no measured success rate, unlike the single-part workflow's real benchmark. Cost is unpredictable and can get steep: one complex assembly run burned ~5.8M tokens for about $13, with no stated guardrail against runaway agent loops. Generated Python is executed with the host user's own permissions; the README is upfront that env-var stripping 'does not sandbox the subprocess,' so this isn't safe to expose or run against untrusted prompts without your own sandboxing.
We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →