Skip to main content

The AI-designed bot is finally begging to be built!

My AI engineering agent designed a DIY robot: requirements, CAD, firmware, simulation. Now it's time to build it.

Automatically translated from German · Read the original

Julian Weyer
Julian Weyer October 11, 2026 · 3 min read
AI ·AI ·Engineering ·3 min read

Some time ago I started building an autonomous engineering agent (hoping it wouldn’t turn against me…) — and now it’s time: its creation has been designed, calculated and simulated, and the firmware is written: The creature is pawing at the ground with its “hooves” and wants to be built!

The design in numbers

The video above shows how impatient the robot has become. Time for a few key figures: what actually happened between “Hey computer, can you develop a small DIY robot?” and the demand to be built?

The AI-developed DIY bot in numbers 60 commits, 12 chat sessions, 6 handoffs, 44 requirements, 22 test cases, 5 change requests, 17 architecture decisions, roughly 8,500 lines of code, 6 simulation studies with 80 individual runs and a calculated price of 74.70 euros. AI-DEVELOPED DIY BOT in numbers 60 Commits over 6 working days 12 Chat sessions with the AI agent 6 Handoffs questions for the human 44 Requirements 22 stakeholder, 22 system 22 Test cases plus 28 firmware unit tests 5 Change requests changes to process and design 17 ADRs architecture decisions 8,500 Lines of code roughly; Python, C, JavaScript, SysML 6 Simulation studies MuJoCo with the real firmware 80 Individual runs in the latest state, approx. 14 min compute time €74.70 Calculated price 28 items, incl. shipping

Behind the tiles is everything that belongs in any engineering project: requirements, architecture, bill of materials, firmware, test cases and a simulation that sends the robot driving through the living room. The agent calculated the parts at a total cost of €74.70, shipping included.

Driving the robot - with real firmware

You can also try the robot yourself online: the browser demo runs the real firmware with real physics. Admittedly, with a teddy bear and a ball it’s a bit playful — but it’s also genuinely useful. Without this simulation I wouldn’t have caught a few not-so-sensible shortcuts and simplifications my agent had taken.

Not a toy - potential in engineering

The robot is a toy, but my “operating model” behind it is not: requirements, architecture, CAD, firmware, simulation, all linked together. Especially for customer-specific project work and special-purpose machinery, where variations of the same technology keep coming up, there is enormous potential for comparable use cases. For a look at how I set up the agent for this, see the post on the operating model. Direction is still set by the human.

PLM and ALM are my day-to-day business at BHC / PROSTEP, and the Digital Thread is my topic. An agent that runs through this chain on its own shows quite directly where the field is heading. If you want to think this through for your own engineering process: get in touch.

Now it gets built

The shopping list is written, now it’s my turn: sourcing, soldering, screwing. Whether the robot does in reality what it promises in the simulation remains to be seen.

To be continued: it’s getting built!