Is Vibe Manufacturing the Next Vibe Coding?

Business Insider just published a fun piece on what people are calling "vibe manufacturing": describing a physical object to a chatbot, getting back a CAD file, and having it fabricated. If you've been anywhere near the "vibe coding" discourse, the shape is instantly familiar.

The examples, all from Henry Chandonnet's article:

• A real estate developer described a steel bracket for his camper by voice, and the chatbot produced a DXF, opened SendCutSend's website, filled in the order form and paid the $156 with his stored payment info. The part arrived ten days later and fit.
• A robotics hobbyist got a sheet-metal robot arm fabricated for about $200, but only after earlier iterations with loose screw holes and "compounding failures" burned through about $2,000 of reorders.
• An IT worker built a storytelling toy for his daughter: a week of modeling instead of months, then he had a second chatbot criticize the first one's design until they reached a consensus, and ordered ten units from JLCPCB for about 500 euros.
• A tinkerer building an answering box for his kids has printed the case around fifteen times and counting. His review: "AI's good but not perfect."

Worth reading the original. What I want to add is the developer's version, because if you write code, you've seen this exact movie.

The test suite got slower and pricier

With vibe coding, the prompt is the visible ten percent and the gap to production is the work. Vibe manufacturing has the same shape, but the feedback loop changed its physics.

A unit test runs in milliseconds and costs nothing. A fabricated part takes days and real money, and a wrong dimension doesn't throw an exception. It arrives at your door as plastic or steel. The bracket builder got lucky: he says he was sure it would be a millimeter off, and it wasn't. The robot arm builder paid $2,000 to learn what a failing test feels like when each test run costs $200.

So the skill that transfers from software isn't prompting. It's the review loop. Everything below is code review and testing habits, translated into atoms.

Ask for code, not sculpture

This is the one concrete thing I'd push on if you try this: pay attention to what format the AI gives you back.

If it gives you a mesh, an STL blob of triangles, you have a statue. You can measure and even edit meshes in mesh software, but the original design history is gone: no named dimensions, no constraints, no record of why that hole is 4mm. A change that should be one number becomes manual sculpting, and when the part comes back wrong the tempting move is to re-roll the prompt and hope.

If it gives you parametric CAD as code, you have something reviewable. OpenSCAD and CadQuery both describe a part as code: named dimensions, constraints, relationships. OpenSCAD has its own little scripting language; CadQuery is plain Python. You can read the hole diameter before you pay for it. You can change 4mm to 5mm without regenerating the whole part. You can put the design in git and diff revisions, which is a genuinely strange sentence to write about a physical object, and also exactly what you want.

There's a middle route too: tools like Zoo's Text-to-CAD generate actual B-rep models, real CAD solids rather than meshes. You don't get a readable script that way, but you do get a solid you can open in CAD software, measure properly and modify, which beats a bag of triangles. The Business Insider piece mentions an open-source text-to-CAD project that already tops 23,000 GitHub stars. The direction is clear: the useful tools in this space will be the ones whose output you can inspect and modify, not the ones that hand you a finished-looking blob.

And note what the toy builder did: he asked a second model to criticize the first model's design. That's a design review. He ran a pull request process on a toy.

Print the smallest test first

In software you don't deploy the whole system to find out if one interface is wrong. Same instinct here: before the full part, fabricate the cheapest thing that proves the risky assumption. A hole pattern. A mating surface. A ten-minute print of the one corner where two pieces meet.

The answering box builder's fifteen prints of the same case sound excessive until you realize that's just the iteration loop, run at home-printer prices instead of fabrication-service prices. Each print was a test run. The bracket that fit perfectly on the first try is the outlier, not the plan.

The no-ship list

There's a difference between a hobby prototype and a validated safe design, and every one of these projects sits on the prototype side of that line. The article is honest about it: the more complex the product, the harder this gets, and nobody is vibe manufacturing a car.

Some things should stay on the no-ship list until they get qualified engineering review and whatever safety and compliance testing applies to them: anything load-bearing, anything safety-critical, anything touching mains voltage, food-contact surfaces, and products for other people's kids. Two chatbots reaching a consensus is a great prototyping trick. It is not an engineering review, and it is not a safety test.

Also, one detail in the article deserves more attention than it got: the chatbot ordered and paid for the bracket itself, using the developer's stored payment details. An agent that can place fabrication orders with your card needs a written spending boundary before it needs anything else. That part made me more nervous than any of the geometry.

Where this actually is today

Read the examples again and a pattern shows up: brackets, jewelry, a brain model, toys, a robot arm the builder calls "edutainment". Personal prototypes and learning projects. The people closest to a product say versions of the same thing: fun to prototype, not ready for a factory.

That matches where vibe coding was a couple of years ago. The prompt got cheap; the review didn't. So if you try vibe manufacturing, bring the boring skills: read the dimensions, test small, budget for iteration, and keep a human between the AI and anything that has to actually work.

The machine can speak a part into existence. Somebody still has to check its homework.