Uploaded October 2026 | Updated November 2026, 19 hours ago
I hand-modeled a futuristic chess set in Houdini and it took forever. A year later, AI agents design printable parts for me, and they even add details I forgot to ask for. So what's actually left for me to do?
This is how GeometryForge came to be: from hand modeling, to parametric build123d code for my ant colony, to an agent that designs a sci-fi LED box for a hole in my office wall, with editable Blender and Houdini files. Along the way: versions, generation runs and tests that every change has to pass, a nut trap I never asked for, and the two decisions the agent got wrong because it couldn't know what was inside my wall.
GeometryForge is open source: an agent skill for Codex and Claude Code, plus a thin local 3D viewer to inspect parts and compare runs.
→ github.com/DavidKahl/GeometryForge
Chapters
0:00 Cold open
0:42 A printer and a familiar feeling
1:14 A chess set from 2083
2:58 The ants
5:26 Why GeometryForge became a tool
7:00 A box for a real problem
9:10 The first run
11:18 What I didn't say
13:13 So what do I do with all this?
14:16 What GeometryForge is now
15:51 Close
About the visuals
Prints, photos, printer timelapses and screen recordings are real. Concept images (chess, the novel, the rocket's reference image), photo animations and the illustrations marked as AI concepts were generated with AI. Preview renders and the Blender/Houdini files were made by the agent. The rocket was modeled and sliced, not printed.
The wall box is a personal prototype. Fit and geometry checks don't make it an electrical product. If you're working with mains wiring, follow your local rules and use a qualified electrician.
Use AI, but don't skip the fundamentals.
#3Dprinting #AIagents #GeometryForge
I hand-modeled a futuristic chess set in Houdini and it took forever. A year later, AI agents design printable parts for me, and they even add details I forgot to ask for. So what's actually left for me to do?
This is how GeometryForge came to be: from hand modeling, to parametric build123d code for my ant colony, to an agent that designs a sci-fi LED box for a hole in my office wall, with editable Blender and Houdini files. Along the way: versions, generation runs and tests that every change has to pass, a nut trap I never asked for, and the two decisions the agent got wrong because it couldn't know what was inside my wall.
GeometryForge is open source: an agent skill for Codex and Claude Code, plus a thin local 3D viewer to inspect parts and compare runs.
→ github.com/DavidKahl/GeometryForge
Chapters
0:00 Cold open
0:42 A printer and a familiar feeling
1:14 A chess set from 2083
2:58 The ants
5:26 Why GeometryForge became a tool
7:00 A box for a real problem
9:10 The first run
11:18 What I didn't say
13:13 So what do I do with all this?
14:16 What GeometryForge is now
15:51 Close
About the visuals
Prints, photos, printer timelapses and screen recordings are real. Concept images (chess, the novel, the rocket's reference image), photo animations and the illustrations marked as AI concepts were generated with AI. Preview renders and the Blender/Houdini files were made by the agent. The rocket was modeled and sliced, not printed.
The wall box is a personal prototype. Fit and geometry checks don't make it an electrical product. If you're working with mains wiring, follow your local rules and use a qualified electrician.
Use AI, but don't skip the fundamentals.
#3Dprinting #AIagents #GeometryForge










