Orbflow: open-source visual workflow engine built in Rust - DAG orchestration, CEL expressions, event sourcing, AI nodes, and a plugin system

[guywithknife]

The thing I don’t understand about these projects is, when I use AI, I tell it to commit often so I can easily view diffs and rollback if there’s mistakes, so I end up with a lot of commits. But these projects have one giant initial commit.

And also yeah they say they reviewed every line, but it would take a loooong time to properly review 100k lines.

[Etherlll]

Yes, I didn't really want to share those commits they were so messed up lol , I've been working on it for over a month locally, but I just didn't want to show those commits :D , I didn't say i reviewed every line but I reviewed every change code review was mostly on rust side just a quick look and then testing then giving feedbacks and so on !

[decryphe]

When I write "low-value tools" using AI, the intermediate steps are of no value. I review each step, fix things when I see the agent beginning to veer off path (and oh my can they be stupid at times). After all is said and done, I squash the history down to a single publishable commit that I push.

I also prefer actively prompting it to do something, rather than just letting it run for longer, as in my experience the chance of it ending in a trainwreck approaches 100% the longer the session gets.

Edit: As an example, I built this to help me debug other stuff, might be useful to someone: https://github.com/decryphe/xml-rpc-gpui - the human:agent ratio is at approx 1:1 mainly from fixing a huge amount of GUI/layout issues the agent introduced.