possible. Since Pi exposes so much, it is very easy to build advanced tooling around it to help easily grok hundreds of tool calls to help you understand what they agent knows and what it has tried.
Recommendation? No. Just go with the passive-aggressive advice "let pi build it for you". :-)
To be more constructive, what I did (as an experiencd SWE but a complete noob to agentic coding): went to pi.dev's extension marketplace and looked into all the new shiny stuff. Subagents, mcps, context and memory optimizers, skills. Using the most popular ones (not necessarily the best ones)
It was like 15years ago learning the new mindset of vim (and spending a ton of time to customize it to my workflow). My understanding is that Claude and opencode doesn't give you this flexibility.
Learning all these stuff drove me to also set up openwebui, and it was such a successful private project that I implemented it at work (with jira/confluence/bazel query access) and management said "we need this by tomorrow".
I believe the models matter not that much anymore. The "harness" does. (unless you just want to vibe code. Thebn, throw crap at fable and call it a day)
omp is not really pi. Its a very distant fork of it. And its philosophy is completely different, it includes everything you need except workflow skills. Personally, I think it is the best agent coding tool by far, and its what I settled on after trying 6+ different tools.
This is self promotional but I am working on making pi extremely enterprise ready with:
https://github.com/gitsense/pi-brains/tree/staging
The README is being worked on but the three videos should give you a good sense of what it can do. Pi is also what makes what I will demo in
https://github.com/gitsense/chat/tree/update-readme
possible. Since Pi exposes so much, it is very easy to build advanced tooling around it to help easily grok hundreds of tool calls to help you understand what they agent knows and what it has tried.
Recommendation? No. Just go with the passive-aggressive advice "let pi build it for you". :-)
To be more constructive, what I did (as an experiencd SWE but a complete noob to agentic coding): went to pi.dev's extension marketplace and looked into all the new shiny stuff. Subagents, mcps, context and memory optimizers, skills. Using the most popular ones (not necessarily the best ones)
It was like 15years ago learning the new mindset of vim (and spending a ton of time to customize it to my workflow). My understanding is that Claude and opencode doesn't give you this flexibility.
Learning all these stuff drove me to also set up openwebui, and it was such a successful private project that I implemented it at work (with jira/confluence/bazel query access) and management said "we need this by tomorrow".
I believe the models matter not that much anymore. The "harness" does. (unless you just want to vibe code. Thebn, throw crap at fable and call it a day)
I found that opencode absolutely lets you do everything that pi does. With a few niceties in the UI on top.
Opencode doesn't even allow providing your own system prompt.
Got it :-)
Happy with oh-my-pi (omp)
I looked into it but, at least for me, it goes against the entire philosophy of pi :-)
the entire philosophy of pi is to be extensible
omp is not really pi. Its a very distant fork of it. And its philosophy is completely different, it includes everything you need except workflow skills. Personally, I think it is the best agent coding tool by far, and its what I settled on after trying 6+ different tools.
I've had a lot of fun with https://omp.sh/ - consider it like zsh -> ohmyzsh
Lots of sensible defaults and good tweaks/settings you just don't worry about.
pi-role-model