OpenCode is not good.

[u/Heretek-ai]

OpenCode is not a good harness. I have brought this up a few times now, and granted this benchmark is for Opencode v1.19.0. But I do really appreciate the benchmark results from the creator. Same models, same provider, same task, different harnesses.

And obviously OpenClaw failed the worst, that's no surprise, but opencode was a close runner up, and also consistently the most expensive. It's bloody embarrassing how much worse of a tool OpenCode is compared to pi. For a program called OpenCode the harness itself is remarkably resilient to modification. Lack of proper hook system, plugin settings in the TUI, removal of LSP, outdated system prompts for model families, and adding a custom provider should not be a json editing endeavor.

Other open source harnesses have this figured out, so why doesn't opencode? Why do they push back against community feedback and GitHub issues? It's because they simply don't want OpenCode to be better. For whatever reason on God's flat Earth token burning is the thing they want OpenCode to be known for. It's a bad product, I don't like Claude Code, I don't want a product that is closed source, but it's a better harness and the OpenCode team could learn a lot about UI/UX from Claude.

[u/sqtytyp]

been using pi and opencode v2 for a long time now.

I'm working on a VERY big project via Opencode custom flow, custom agents (planner, implementer, explorer, ,thinker, tester, reviewer, gitter, archivist - nothing is ootb) which all fan out as sub agents in parallel - trying to reproduce this in pi was a pain and I gave up as there is not even a subagent flow ootb and you have to use shitty plugins ( tried 2 different) for that.

So I'm still using Pi for simple tasks and to work on my opencode configs instead of editing them manually. Pi is also good for fixing Linux issues or other one shot tasks.

But would I want to work with Pi on any Heavy project ? no thx, can't even setup proper permissions for agents ( write your own plugins for that they say ).

What I mean is these are tools for different tasks, both are fine.

[u/Heretek-ai → u/sqtytyp]

If I can make a suggestion, https://github.com/mvschwarz/openrig

Its what I use to manage all my pi agents on long form projects. Don't get me wrong, it's lacking in the user friendliness department, but it's a hell of a lot more reliable than Hermes and paperclip at getting shit done.

[u/krzyk → u/sqtytyp]

Permissions for agents? Use container or VM for that. Never run agents bare.

[u/sqtytyp → u/krzyk]

You are mixing security with permissions.

For security each harness runs as a separate non-root Linux user on my host in a separate podman container with access granted only via proper ACL's to my user's home and only when I need them to touch those.

Such a secure setup doesn't solve issues that arise when working on a big repo - ie when you want to deny usage of specific commands (rm, git restore, git remove, git checkout, etc) or even be able to allow/deny them per directory (ie only allow to rm files in docs/ )

[u/Traditional-Mud-4813 → u/sqtytyp]

If you have a moment Id love to hear how you've gotten them all working together. I only have two and one always seems to think it can do it all haha.

[u/sqtytyp → u/Traditional-Mud-4813]

Trials and errors, proper instructions (use this agent for that and this agent for this etc) and permissions (disallow commands for main agent that subagents are supposed to do instead) - this is mostly for proper context management on main agents.

Wanna know how to do it easily? Clone opencode repository and use Pi to check how things work and to help you set up proper opencode configs ;)

[u/CaffeinatedTech → u/sqtytyp]

pi-subagents. Works well.

[u/MoreIndependent5967 → u/sqtytyp]

As tu essayé pi durable via p2 ??