Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Annoying and alarming things about OpenCode

wren.wtf

Post reply on HN
Print view View original

191–200 of 309 posts

Re: Annoying and alarming things about OpenCode

#191

Post by schmorptron »

trollbridge wrote: post #179
dofm wrote: post #128

Earlier quoted context omitted.

I am on this trajectory too; opencode got me started but I tried to understand the way it is working and to do that I would normally read the source code, but the source code is really not fun.

This seems to be quite common. You start with OpenCode (assuming you're someone who skips all the Claude Code hype); then you start thirsting for more, and switch to oh-my-pi. I generally view the kind of code in projects like OpenCode to be the same as binary machine code, and the harness that works on it is the compiler. The source code is the prompts (I guess), except we live in a weird state now we use the existi…

Yeah, this has been my progression as well. Maybe next it'll be just using plain pi when you figured out exactly what you want from omp and what you don't

Re: Annoying and alarming things about OpenCode

#193

Post by qarl2 »

lucideer wrote: post #122
nextaccountic wrote: post #29

Earlier quoted context omitted.

Maybe https://github.com/tontinton/maki

> - Sensible permission system - when the agent runs git diff && rm -rf /, what do you think will happen in your current coding agent? It will treat it as git *. Maki uses tree-sitter to parse the bash command and figure out the permissions requested are git * and rm *. Disable using --yolo. This sounds identical to what OpenCode does (&, contrary to their own marketing, does not seem sensible at all). The fact that…

> The fact that this mechanism is so primitive across all agentic clis is frankly a serious indictment of the competence & experience behind LLM-focused development teams.

Not at all. The proper solution to this problem is running in a sandbox - which is not reinvented by the LLM harness because there are already many great options.

You misunderstand the mechanism. It is not intended to provide security. It is intended to guide LLM behavior.

Re: Annoying and alarming things about OpenCode

#194

Post by dizhn »

kristopolous wrote: post #6

Opencode offers free models with 200/requests over 5 hours. That's why I use it. It is the only reason I care about. What's the alternative there? Gemini used to have free tiers. Qwen used to. AMP used to. Ollama cloud used to. Codebuff used to... None of them have those programs anymore The reason I use it is purely financial. I do not have an employer and I'm writing free software Edit: pi.dev doesn't have free inf…

Currently only Mimo has a usable free offer with their own CLI. (opencode clone)

Re: Annoying and alarming things about OpenCode

#195

Post by dizhn »

kristopolous wrote: post #151
rafram wrote: post #15

Earlier quoted context omitted.

There are other OSS agent harnesses.

That offer free inference? I've written my own. I know they exist. I don't offer free inference on large models however

As I said in other reply there's Mimo. But I would check the opencode Go plan. First month for 5 usd and renewal at 10. (With referral offers too). If you use only deepseek flash it would take you a long way every month.

Re: Annoying and alarming things about OpenCode

#196

Post by dizhn »

est wrote: post #62
kristopolous wrote: post #37

Earlier quoted context omitted.

Can't get those generous free quotas from opencode with that.

hmm you can. https://opencode.ai/zen/v1/models https://opencode.ai/zen/go/v1/models

Go is not free at all (you can't use any of the models you listed without a subscription) and the free Zen models will not be on other CLIs as far as I know.

Re: Annoying and alarming things about OpenCode

#197

Post by qarl2 »

lucideer wrote: post #178
qarl2 wrote: post #98

Earlier quoted context omitted.

I wonder how he imagines you can give shell access but securely prevent arbitrary command execution. His complaint that "echo git | bash" still works is particularly nutty.

This is very doable - it's a shell you're creating within the cli so you have a lot of control over the environment. If you look at tools like sandbox-exec & apparmor, they specifically target binaries, not string input. E.g. if I write a bash script & put it in my path, OpenCode's allowlists aren't looking at the commands my bash script is exec-ing, nor monitoring subshells it creates. A proper sandbox has full cont…

Yes, I am aware that sandboxing technology exists. I use them. I don't expect them to be built into my LLM harness because I value modular software composition - and sandboxing should be provided by a product that specializes in that area.

OpenCode's allowlists are not there for security. They exist for LLM behavior guidance.

Re: Annoying and alarming things about OpenCode

#198

Post by petesergeant »

wren6991 wrote: post #27
petesergeant wrote: post #16

You should absolutely be running your AI agent inside _some_ kind of sandbox. I put together a list of 19 mostly open-source ones here: https://pleasedonotescape.com/ along with a list of non-project-solutions

Yeah, I don't think that line quite landed. My point was that LLMs are inherently adversarial (read, "relentlessly proactive") and sandboxing should be a first-class integral feature of your harness, not an afterthought. The problem with dev containers is you still tend to end up with something you care about on the same side of the trust boundary as the LLM.

> LLMs are inherently adversarial (read, "relentlessly proactive") [and] you still tend to end up with something you care about on the same side of the trust boundary as the LLM

I mean this is a problem with many coworkers too, so you deal with it in the same way: limit what they can do to creating pull requests.

Re: Annoying and alarming things about OpenCode

#199

Post by fallingbananna »

volf_ wrote: post #9

I switched from OpenCode to Pi and there was a big improvement in terms of tool calling performance and I find the experience less buggy. OpenCode has also seemed to have disappeared from https://openrouter.ai/apps/category/coding

Kilo is the top 3 option there, and that's a fork of OpenCode.

Re: Annoying and alarming things about OpenCode

#200

Post by tomku »

dboon wrote: post #164

This prose feels extremely angry and ungenerous; abstractly, I agree with a lot of the points, but when I read this: > My conclusion is that OpenCode is clown-car turboslop with a security posture of “let me bend over for you daddy”. Everyone using it should stop using it. I do not want to keep reading. There are regular people who wrote this software. When did it become normal to talk about open source like this? Ho…

Calling something "vibe-coded" nowadays is a permission slip to unload on it with hyperbole and insults because you can presume there's no human in the line of fire. I really don't think the people engaging in that kind of rhetoric understand how corrosive it is to the humans who do get caught in the crossfire sometimes, and to themselves for normalizing that kind of behavior.
Post reply on HN