Does code-based CAD hold up for real parts, or only for brackets and enclosures?
Agents are writing Verilog and routing PCBs now, but mechanical CAD still looks mostly manual. The usual answer is code-based CAD (CadQuery, build123d, OpenSCAD) since LLMs write Python well.
Has anyone shipped a real part that way, with fillets, draft, drawings, and a vendor handoff? Or is driving SolidWorks/Onshape through the API the better path?
One thoughtful comment unlocks the ability to create threads.
3 comments
@adi or @TheeBigPickle may have good answers to this?
Its rapidly getting better! The newest frontier models (Astra, Fable) can go from basic requirements to a relatively detailed design in short timeframes. The biggest gap IMO is integration with existing CAD softwares; most of them try to drive with HTML and python and struggle to make complex STEP geometry.
Existing geometries can easily be iterated on, though.
I've been designing a custom DAP in my (little) free time. It's CNC machined aluminum with a few different parts including polycarb inserts, and a two piece alu casing that holds the display and the PCBs inside
I've been using Opus 5.5 for the assist and have gotten to the mfg/quoting stage a lot faster than I could without it! My main workflow is Python 2d/sketches -> CadQuery -> STEP -> Solidworks -> edit -> loop