HI version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
67% Positive
Analyzed from 409 words in the discussion.
Trending Topics
#while#github#config#fork#agent#works#great#page#issue#frustrating

Discussion (11 Comments)Read Original on HackerNews
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.
The ticket is closed and this will not be changed, period.
Just make the changes you want to your favorite harness and move on.
In my experience "throw another agent at it/fork it" consistently creates unsupervised trainwrecks.
off: I'm working on my spare time on a code mode lisp alternative (great opportunity to learn lisp) and might switch to it fully as long as I built some simple evals (I'm concerned about token usage, which is why i forked pi the first time)
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.
Edit: Known issue: https://news.ycombinator.com/item?id=49330597
[1] https://github.com/earendil-works/pi/
I use pi and couldn’t care less.