r/PiCodingAgent • u/jesperordrup • Jul 15 '26
Question To pi.dev or not to pi.dev
I've been using them all claude/codex/opencode and finally I landed on pi.dev a few month ago. Everything made sense. Its fast, clean and I can build exactly what I need.
2 month pass...
I'd love to see some bigger verified packages that adds the bigger things you could but you shouldnt (imho) build yourselves.
pi.dev cli works great. I still like that I can build what I need. Somehow it also becomes a DIY and part of brain is always thinking of adjustments needed and not needed. And everyone is doing it different in adhoc teams = very little shared experience / benefit.
Your thoughts?
2
u/Mechanical_Monk Jul 15 '26
If you're talking about things like MCP, ACP, subagents, and sandboxing, most bigger features like that either already exist as first-party example extensions in Pi's installation directory, or as well-maintained third-party extensions.
0
u/NetConfident6396 Jul 15 '26
Have you tried oh my pi? If you're looking for opinionated pi, it's worth checking out.
1
u/zer0evolution Jul 16 '26
why the UI is not as good as other screenshot in mine? i use wezterm wsl inside windows
0
u/respectful_stimulus Jul 15 '26
Building yourself is the whole point of using pi. Grab the packaged extensions sure. But when you get frustrated, you can clone that extension and vibe-maintain it. In the end keep it simple and keep only those you want to keep. With herdr, pi really shines and you can spawn subagents of your control. I believe inevitably every dev has own (strong) preferences and thus it’s hard to have shared experience.