> Pi is Lindy ↗. It’s been around for a year and has arguably the biggest developer community across all harnesses. It’s here to stay.
BTW this isn’t what Lindy really means
> Pi is Lindy ↗. It’s been around for a year and has arguably the biggest developer community across all harnesses. It’s here to stay.
BTW this isn’t what Lindy really means
However, this is very much a “build what you need” type of harness. You have to be willing to use other people’s extensions or build/vibe your own before the harness is useful.
Why I find pi better:
- multi-provider/inference API support out of the box
- greater visibility into token flow/usage
- minimal system prompt
- no hand holding/decisions made for you on what your agents can/cannot do
- extremely customizable
- stable, minimal bugs in the base harness that I’ve experienced
- minimal feature bloat
It’s a great harness for someone who wants extreme control and adaptability. I don’t recommend it to my peers and colleagues who aren’t into tinkering.
For them/me, omp (https://omp.sh/) is excellent and batteries-included. Pi = Linux kernel, omp = Linux/GNU.
This from the post is why I landed on Pi
"What makes Pi the best fit here? Simple: it’s the only harness today that’s open source, vendor-agnostic, extensible, and minimal enough to not force opinions on you. It gives you full ownership and puts you in control. Being able to change the providers without switching apps alone is reason enough to adopt it, but the fact that it’s also so flexible makes it almost impossible for me to switch back."
I am building my own (intentionally simple) subagent orchestration framework inside Pi and am watching Pi Durable closely as I suspect it and Pi will unify before long and subagents are better supported in Durable. (Relatively uninformed opinion in this case, not using Durable yet.)
Edit-typo
The only place showing some numbers is https://frontierharness.org/ but it isn't really up to date, it's easy to test yourself though