Stop Using OpenCode

Users roast OpenCode as a buggy freebie some say they literally can’t quit

TLDR: A harsh blog post says OpenCode, an AI coding helper, is so flawed and risky that people should stop using it. Commenters split between cheering the takedown, mocking the over-the-top writing, and admitting they still rely on it because free options are disappearing.

The big mood around OpenCode is less “helpful coding assistant” and more public dragging with popcorn. The article itself absolutely unloads on the tool, calling it wildly broken, painfully slow, and so careless with safety that the author basically says everyone should stop using it immediately. For non-tech readers: OpenCode is software that helps people write code with artificial intelligence, and this post argues it can make bad decisions while also handling your computer in risky ways. That alone would be spicy — but the comments are where the real show begins.

Some readers wanted to turn the rant into a full-on takedown campaign, with one person saying this could be split into a whole series of bug reports on the project’s page. Others went even broader, reading the post as a not-so-secret argument against using any AI coding helper at all. One commenter basically rolled their eyes and said: if the advice is don’t use this, don’t use online models, and don’t even trust common safety wrappers, then just say you hate AI for software work.

But the most relatable twist came from the bargain-hunter crowd. One user flatly admitted they use OpenCode for one reason: it’s free enough. That turned the discussion from “is this good?” into “what are broke developers supposed to do instead?” And then came the comedy relief: a reader nominated the article’s opening line — featuring a boot, a face, and TypeScript — for a fake literary award in the Tortured Metaphor category. Brutal, nerdy, and extremely on brand.

Key Points

  • The article analyzes OpenCode, an open-source AI coding agent, and says the review is based on source code from git version baef5cd4.
  • It states that OpenCode had 161,000 GitHub stars and describes it as, in the author’s view, the most popular open-source coding agent.
  • The excerpt focuses on prompt-cache behavior in local LLM workflows that use APIs similar to OpenAI’s /v1/chat/completions interface.
  • The article explains that local LLM performance depends on cached prompt prefixes because prefill can be significantly more compute-intensive than token generation.
  • It lists several OpenCode behaviors that the author says trigger prompt cache misses, including rereading AGENTS.md, pruning tool-call context, invalidating context on interruptions, and inserting the current date into the initial system prompt.

Hottest takes

"This could be a series of issues on the opencode repo" — alightsoul
"May as well write a post saying don't use LLM's for any SWE work" — htrp
"Bulwer-Lytton prize in the Tortured Metaphor category" — chuckadams
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.