why pi over opencode? earnestly curious, trying to figure out what open solution people are consolidating on. (codex is also pseudo-open but contributions closed and nice)
pi is the neovim of agentic harnesses, its barebones and extremely configurable. if you're the sort of person who likes that sort of things its a forever product, nothing is going to displace it because you have full control.
opencode builds a lot more in, which is better if you dont want to fiddle with config.
nice. i had thought the consensus had moved pretty firmly towards pi, so i was surprised to see Thinking Machines demoing their new model Inkling in OpenCode. wondering if they are previewing an acquisition
Most of my harness experience is with Claude Code and Pi, a little bit of OpenCode.
I like how quick and snappy Pi is, it feels like a minimal harness, just enough to manage the agent and get out of the way. Earlier models also seemed to have an easier time working with the tools, e.g. GPT-OSS-20B is about a year old and had no trouble in Pi.
I imagine because they want to support plugins, and plugins in compiled language are a lot less natural than plugins in languages like TypeScript or Python.
why pi over opencode? earnestly curious, trying to figure out what open solution people are consolidating on. (codex is also pseudo-open but contributions closed and nice)
pi is the neovim of agentic harnesses, its barebones and extremely configurable. if you're the sort of person who likes that sort of things its a forever product, nothing is going to displace it because you have full control.
opencode builds a lot more in, which is better if you dont want to fiddle with config.
nice. i had thought the consensus had moved pretty firmly towards pi, so i was surprised to see Thinking Machines demoing their new model Inkling in OpenCode. wondering if they are previewing an acquisition
Most of my harness experience is with Claude Code and Pi, a little bit of OpenCode.
I like how quick and snappy Pi is, it feels like a minimal harness, just enough to manage the agent and get out of the way. Earlier models also seemed to have an easier time working with the tools, e.g. GPT-OSS-20B is about a year old and had no trouble in Pi.
Opencode gives you better defaults and a Mac/Windows app for free but pi is much more extensible and portable.
Pi is good in concept, but why couldn’t they choose a compiled language instead of TypeScript?
since pi is built to modify itself, isn't it better to use a language like typescript where LLMs have a LOT of training data?
a harness doesn't do any computations by itself so what benefit is using a compiled language?
i find LLMs generally play better with compiled languages actually, they do great with rust. you can think of it almost as analogous to a harness.
1 reply →
I imagine because they want to support plugins, and plugins in compiled language are a lot less natural than plugins in languages like TypeScript or Python.
Why does it matter? Agent harnesses aren't doing anything that would make a compiled language more suitable than a scripting language.
For TUIs, Rust/Go vs Typescript doesn't really makes a huge performance difference and you lose the 50x bigger community advantage of Typescript.
I would imagine the extension system they built would be much more difficult to manage. They could have opted for Lua, though, I suppose.
Does it matter to you as a user, other than the Nodejs/npm requirement?
Sorry for self-insert, but that's exactly what I thought and I built https://github.com/gi-dellav/zerostack, so you are right I'd say
Opencode is written in Go.
It is written in Typescript.
https://github.com/anomalyco/opencode
There is an archived Opencode project written in Go but I don't think it is affiliated.
https://github.com/opencode-ai/opencode
1 reply →
I recommend using https://omnigent.ai over Grok Build or any other harness.
This is not how to push your own product - there's no value add to your comment, and you don't even have a disclaimer that you are involved with it
As a general rule I don't use new products whose websites don't resize properly on mobile.
If you fuck that up, makes me wonder what other obvious stuff you fuck up.
thanks for the feedback! there is no excuse for it, and I just pushed a fix for our website to look better on mobile.
if there is any other obvious stuff that's broken we are happy to take the feedback and fix it. :)
1 reply →
I tried twice and ran into bugs that prevented me to trust it
appreciate for trying! if you have the time, we would also appreciate if you can send these bugs our way so we can fix them :)