Hacker News new | ask | show | jobs
by alexgarden 106 days ago
Vibe coding hardware. Nice.

Super cool idea, and I like the hierarchy view - looks like SolidWorks / OnShape, but your UI's pretty flaky; it keeps chasing the solution. If you could make that part more robust, it would be more fun. I did enjoy my "anthropomorphize a unicorn taking off in flight like Superman" model. Does ordering actually work, or is this still a test?
1 comments
ronaldluc 106 days ago
Good point. It's flaky, because the orchestration is fully Opus driven. It has tools, skills, multiple turns. I was inspired inspired by the OpenClaw system. The UX should improve the most by tuning the internal `.md`s, but I'm also thinking about adding stricter workflow for each type of physical product like https://github.com/obra/superpowers does. Toys, enclosures, statues, servo robots, all need different amount of user feedback and artifact refinement.

Yeah, ordering actually works, we just had the first order :)

link
alexgarden 106 days ago
FWIW, I chased this demon early-days in my multi-agent orchestrated harnesses. you'll need a state machine. i used locally hosted temporal.io. it's a bit of a PITA to set up but it whips the llama's ass once it's running.
link
ronaldluc 106 days ago
Okey, went through temporal.io and prompted how could it be implemented into our workflow It actually can replace the semaphores, checkpointing, cancellation and even add crash recovery (since it's for free, why not).

But I don't understand what makes it a state machine. Temporal sounds like durable execution enabler. It is better fit to sit on top of our state machine.

link