alt Hacker News> I really don't mean to discourage anyone but I find that making your own harness is pretty complex process. We where very naive when we started, thinking this is just a loop, but then it turned out it has all kinds of nuances, edge-cases, things to be considered, etc.
I'd be interested in your harness if its open source, please share some more resources
> Pi.dev, Hermes and all the other I have seen do not do even half of the things I have enumerated above - not at least out of the box.
Interesting that they don't do these things out of the box, do you still have some ideal setup then though? Like Pi.dev + X/Y/Z thing which can make things work close enough to ideal.
Because although our conversation is interesting, I feel like I am unable to take any enforcable action and I might default back to opencode. So I would love if you could talk more about it.
Replies
https://github.com/can1357/oh-my-pi
Pi+some additions here. Have not used it enough to have a strong opinion, however, I’ve seen it mentioned here.
I am not saying that they do not work.
What I am saying is that they do not handle many things that we handle internally and yes our code is not open source so I have the luxury to compare notes without revealing much how we do things... sorry about this.
The reason opencode and pi.dev are not handling a lot of the edge-cases is because they are primarily designed to run in a constraint mode with some level of human intervention assumed and while you can certainly make them run in yolo mode I don't believe this is most of their usage. OpenClaw is like that but then look at the code behind it - it is enormous. Most of it is mysterious to me.
Our tool is my bio. But for open source opencode and pi.dev are the best and most widely used.