Their security track record.

https://wren.wtf/shower-thoughts/stop-using-opencode/

I know people who really like OpenCode. I think the experience is pretty similar to Claude Code in that it's set up, out the box, with a specific wat of working. If you like it, then great, if not, you're kinda stuck.

Obviously you can add skills/rules/prompts/etc, but I don't find those are particularly great at being stuck to.

Pi is much more minimal, so if you have strong opinions about how you want to work with LLMs, you'll have a much better chance of bending the to your will.

OpenCode is a worse design in several ways. But the worst part is they don't really respond to issues or pull requests and support is nonexistent. Been in multiple issues with a dozen people begging for a fix with no response. So we all do what we can but there's no one community fix. A ton of OpenCode functionality gets broken constantly because they have almost nonexistent regression tests nor e2e tests for all the features. When they do break it you have to go to Discord and hope someone from their team sees that they broke something, and hope they want to fix it or take a PR for it. This is also ignoring the massive memory leaks that were just accepted as normal.

But with Pi being barebones and intended to be customized, there are a million extensions to choose from compared to OpenCode. This means not only can you write your own extension easily, 5 other people already have. I forked one popular question-asking tool and added support for an external ui (Zenity). And an LLM provider (Synthetic) had a bug which I helped get fixed in a 3rd party extension for the provider. Both I got done in days, because I didn't have to go through some official Pi team; extensions distribute the work better. It's still hard to manage all the extensions, but better than the alternative.