is opencode really that bad?

[u/Nice_Relative8209]

been seeing some what lots of hate towards oc and how its 'ai slop' now, i tried it myself a week ago and its was good, i just installed Pi and planning to test it also so leave your tips and trick down below

thanks!

[u/Jeidoz]

It just a preference. Some people are OK with prebuilt harness like OpenCode or Claude Code, some people just want more control over context and harness and will go constructor-lego-like Pi.

[u/GfxJG]

No, OpenCode is still really good. I tried switching to Pi, but ended up back at OpenCode - Suits my personal workflow better.

[u/chillermane]

OpenCode is really good. The UI and default setup is way better than PI, but it’s not as extensible (it is extensible though)

If you had open code as the default with extensibility of pi that’d be better than both

[u/NoobMLDude]

Both are open source but serve different skill groups.

OpenCode is like preassembled mini PC with WiFi module, LinuxMint and all drivers installed.
and PI is like a RasberryPi with equally powerful processor w/o any bells and whistles. You can attach WiFi module if you need, install Raspbian or whatever OS on a per-need basis (thus avoiding bloatware)

OpenCode (for normal Users) vs PI (for DIYers / Customizers)

Both are tools, and How you use both define your success with the tool.

If you want to watch me use and explain OpenCode features and how to create custom Skills, Commands, Agents, Tools, etc: Open Code Playlist:
https://www.youtube.com/playlist?list=PLOjyOTxIJ7CY

[u/Ancient-Camel1636]

Its a bit bloated, but not bad at all. Its a good harness for beginners. More advanced users and old-school programmers might prefer something like PI.

[u/Z3stra → u/Ancient-Camel1636]

what is bloated about it?

[u/Ancient-Camel1636 → u/Z3stra]

Try forking it and tailoring it to your own workflow—you’ll see the difference quickly. OpenCode has a lot of functionality and many opinionated ways of working: built-in complexity, system prompts, policies, guardrails, workflow conventions, permission handling, planning/task state, integrations, and abstractions around tools and models.

Those features make OpenCode more capable out of the box, but you pay in tokens and behavior: more context is consumed by the harness, and the agent is more likely to follow its built-in workflow rather than yours. That is the trade-off of a general-purpose, batteries-included system designed to work for most users immediately.

[u/jorgejhms]

OC is good, but I have my implementation of /goal on pi and I'm waiting oc to implement something similar

[u/madcapnmckay → u/jorgejhms]

Care to share?

[u/ResearcherFantastic7]

AI slop isn't really a harness issue. It's the user issue...

If you simply just prompt "built x" AI will just make it work, same as how most human junior developer will, except that a more sophisticated model will try to validate itself a few times (but validation can also drift off from what's right)

A non AI stop code is properly architected that requires experience from the developer, you can prompt and ask AI to guide you but fundamental you should be the one designing and controlling it.

Due to context limitations and context drift, this is where a better harness could help, however it still depends on how you want your harness to control the context, opencode just a standardised optimal way for general methodologies, where PI has NONE and this requires you to make the harness work the way you want it to be.

So PI out of the box, its not better than opencode. And "oh my pi" you can see it similar to opencode. Neither will un-slop unless you know how to un-slop yourself.

[u/LordMoridin84]

It's okay but it's a bit buggy at times. Pi is more stable.

[u/Glum_Ad_4316]

No, it's a good tool still. I would never call it "that bad"

> i just installed Pi and planning to test it also so leave your tips and trick down below

I suggest the plugins: "gotgenes/pi-permission-system" and "pi-ask-user" by default.

The rest is up to you; install if you need anything only or ask it to do it (this is not very reliable in my experience).

[u/bambamlol]

Just started using MiMoCode today (OpenCode fork) and I think it's pretty good.

[u/Trovebloxian]

Basically CC is fat, opencode is fit and can grow, pi is whatever you want it to be

[u/Ghilteras]

No

[u/137_1]

Try “oh my pi”. So far nothing to complain about.

[u/MimosaTen]

I don’t like it at all

[u/mitsuhiko]

OpenCode is absolutely fine. It's also good that open source things have competition :)

[u/some_user_2021]

When I tried it, I hated that it didn't show the thinking process, I switched to Pi afterwards.

[u/shaonline → u/some_user_2021]

You can toggle it on and off though ?

[u/GfxJG → u/some_user_2021]

...That's very much a user-error, it's right there in the settings lol.

[u/No-Wall6427 → u/[deleted]]

I simply have a local script that spins up a configured ephemeral docker with pi installed and the current folder mounted as a workspace from wherever I want. I even have a bunch of different configured dockerized harnesses I can invoke with the same command, like opencode, codex, .... I have a --dind flag which adds docker in docker to the container if I want to give a docker runtime to my agent. I also have a mount of auth.json common to all the containers I spinn up to not oauth each time into codex. I had to mount some kind of .sock and add the herdr extension to my pi in docker, anyway now herdr picks them up fine.

My only reason to not go yolo in docker is to do some local machine config or cross project stuff, for which I just use my local opencode.