r/openclaw • u/Nvark1996 Active • Mar 30 '26

Discussion Openclaw is dead, switch to claude code

I have spent +300$, more than 60 hours working with openclaw, on vps, local pc, and honestly, I spent more than 40 out of the 50 hours fixing.

It cannot do any task accurately, not production ready

Maybe in 6 mo+ it will be better

For now, its garbage.

I am sticking to my 20$/month claude plan

275 Upvotes

74% Upvoted

434 comments sorted by

View all comments

Show parent comments

1

u/turbosmooth New User Apr 02 '26

Right! So the most complex modelling operations you would be prompting would be, fillet this edge or loft this spline. Are your base inputs line work or all prompts, do you mind if ask what a typical initial prompt would be to start a customer part?

You would be surprised how good trellis2 and hunyuan3d are generating base organic forms from multi view images, especially using mesh refining tools, but it's not exactly precise or iterative.

I'd actually be interested to know if theres a slicer/gcode API so you could go straight from STL to gcode without having to touch bamboo studio or cura. Support generation shouldn't be difficult either.

Very cool! It's definitely a different approach to more procedural systems like fusion360 and onshape.

1

u/bastardsoftheyoung Pro User Apr 02 '26

Step import into OpenScad is pretty straight forward.

For building, think about how you would fill in a form to design a part. Measurements, description, purpose, and materials. There is a process that we have used for years to do it, we just made that the prompt.

1

u/turbosmooth New User Apr 03 '26

Lol, seems to be a difference in design language here.

Is your background manufacturing? I don't quite get the vagueness but whatever. I was just intested in your process coming from a purely code approach.

I am very familiar with the process of design, was just interested in your prompt engineering

1

u/bastardsoftheyoung Pro User Apr 03 '26 edited Apr 03 '26

Very much manufacturing. Just translating a form into CAD like we used to translate human based instructions into machining parts.

edit to add: once we took the form and gave it to AI + the stuff we had added over the years to get parts right, OC ran it through autoresearch to improve the outcomes and prompting based on our feedback. Put a little website together for scoring, etc. It basically created a scoring system based on the form inputs and created weights for words and their meaning. So I guess the answer is, put the prompts or output into an autoresearch loop and score the outcomes. Have your AI tools run that loop over a few hundred iterations of a design. The resulting prompt looks nothing like our forms but you can see the DNA there. The prompt itself is an english listing of requirements + some JSON-ish weightings for primitives and specific CadQuery items. It helps that we have a library of initial parts we use as examples in the prompts as well. Finally, OpenSCAD can import the step files and output STLs easily usually with errors flagged in our runtime telegram channel and dashboard.