Systemerror7A69
2 hours ago
This has been frustrating me for a while and is part of why I explore other coding agents.
As many advantages as pi has in some areas, there are definitely areas where I believe the hype to be a bit overstated. While the config folder is, ultimately, not relevant for performance, how this was and is continued to handled is a bit frustrating for me.
They have made it abundantly clear it's not going to change however so I'm looking at how other coding agents perform currently.
fny
2 hours ago
LLMs make it gloriously simple to fork and patch and existing repo. If you run into a merge conflict down the line, its a snap to fix too.
Just make the changes you want to your favorite harness and move on.
coldbrewed
an hour ago
In practice this requires duplicating the upstream build and release pipelines, so now you need yet another agent running in the background (+ periodically going off the rails + eating tokens) which incurs more up front cost and cognitive overhead.
In my experience "throw another agent at it/fork it" consistently creates unsupervised trainwrecks.
Systemerror7A69
an hour ago
Sure but I'm really not that invested in one single harness. I tried out pi because people were recommending it so much. It turns out I personally have some things which annoy me, so I try out others now as well.
If I don't find anything which fits me I might fork it, but even that little effort is not really worth it if theres something which fits me better.
I already found maki which...seems to do the exact same job pi did for me, and I wanna check out crush as well.