Annoying and alarming things about OpenCode • Hacker News Board

Re: Annoying and alarming things about OpenCode

#111

Post by Jcampuzano2 » Mon, Jul 20, 2026, 2:17 PM UTC

lkjdsklf wrote: post #53

the_mitsuhiko wrote: post #35

Earlier quoted context omitted.

> How you deal with LSP? One of the best things in OpenCode is LSP integration. I would love to learn how LSP helps you. I did various basic evals with LSP and I did not find it to improve the agent performance at all. Maybe on newer models this gets better because they are now RLing with LSP in the context, but at least in the past having a commit hook that runs lints and typecheck at the end, is more token efficien…

lsp integration isn't for checks like that. It's for using lsp to do things like symbol renames. It's cheaper to call an LSP server to do those kind of simple refactors than to spend tokens on the model doing it. It can also use LSP to build context without having to grep around a ton. You don't have to grep and hten pull lines and make guesses for a function. You just ask the LSP for it. How helpful all that is is h…

To be fair in every harness I've ever used that has LSP support, they never actually utilize the LSP for more deterministic refactoring tools. And even then when I do enable the LSP in many harnesses oftentimes it doesn't even use it at all.

Maybe they haven't been taught to do so or it's not integrated into the system prompt or the tools but all of them only ever use the LSP to read files/symbols.

Every harness I've used will happily just call the edit tool over and over or do a find and replace via sed or programatically call a python/perl script rather than rename a symbol via other means.

Re: Annoying and alarming things about OpenCode

#112

Post by alightsoul » Mon, Jul 20, 2026, 2:18 PM UTC

nylonstrung wrote: post #105

LaurensBER wrote: post #12

I feel that a better title for this article would be: "Some minor annoyances that, when fixed, would improve OpenCode" # Prompt Cache Misses > It globs your filesystem and re-reads AGENTS.md (injected in turn-0 system prompt) on every SSE turn. If you put a quick note in AGENTS.md to be read in the next session, you immediately force a full re-evaluation. > Personal favourite: it puts the current date in the turn-0 s…

The bigger point is that the codebase is hopelessly bloated by vibe coded features at this point, mirroring the same problems with Claude Code. And stability, performance, memory use have all gotten terrible. I liked Opencode a lot previously but there's no doubt it's not well-written software. Pi has fully replaced it for me and there are quite a few newer options that learned from Opencode and exercise more minimal…

Can you name a few? I'm looking for alternatives

Re: Annoying and alarming things about OpenCode

#113

Post by saghm » Mon, Jul 20, 2026, 2:18 PM UTC

evnp wrote: post #101

chuckadams wrote: post #7

> If you don’t know what OpenCode is, imagine a boot stamping on a human face forever. The boot is made of TypeScript and the face is everything we have learned about security and systems software since the invention of the electronic computer in the 1940s. I nominate this for a Bulwer-Lytton prize in the Tortured Metaphor category.

"There will be no curiosity, no enjoyment of the process of life. All competing pleasures will be destroyed. But always— do not forget this, Winston— always there will be the intoxication of power, constantly increasing and constantly growing subtler. Always, at every moment, there will be the thrill of victory, the sensation of trampling on an enemy who is helpless. If you want a picture of the future, imagine a boo…

That would be an example of a non-torturted metaphor. When you copy the famous quote verbatim and then substitute both parts of it for things that are almost entirely unrelated, it becomes tortured.

Re: Annoying and alarming things about OpenCode

#114

Post by versteegen » Mon, Jul 20, 2026, 2:19 PM UTC

LaurensBER wrote: post #12

I feel that a better title for this article would be: "Some minor annoyances that, when fixed, would improve OpenCode" # Prompt Cache Misses > It globs your filesystem and re-reads AGENTS.md (injected in turn-0 system prompt) on every SSE turn. If you put a quick note in AGENTS.md to be read in the next session, you immediately force a full re-evaluation. > Personal favourite: it puts the current date in the turn-0 s…

I always run opencode with envvar `OPENCODE_DISABLE_AUTOCOMPACT=1` because I discover a new horrible bug in its autocompact every time I don't... including the config .json option to turn off autocompact not working.

Sad but not surprised to hear about all these other issues. I like opencode, it does plenty right but plenty wrong.

Re: Annoying and alarming things about OpenCode

#115

Post by jacobgold » Mon, Jul 20, 2026, 2:20 PM UTC

I really hope truly open models and local inference are the future.

But are there are any reasons a pragmatic and informed developer would use OpenCode vs Claude/Codex as a harness today?

I'm not seeing anything competitive in terms of cost/quality/trust?

Re: Annoying and alarming things about OpenCode

#116

Post by simonw » Mon, Jul 20, 2026, 2:20 PM UTC

Including the date in the system prompt - at the cost of a cache invalidation at midnight - is an entirely reasonable decision. Most other harnesses do the same thing.

Including the full datetime would be irresponsible, but that's not what OpenCode does.

Re: Annoying and alarming things about OpenCode

#117

Post by wagslane » Mon, Jul 20, 2026, 2:21 PM UTC

A more accurate title would be "The Problem with AI Agent Harnesses, and small annoyances with OpenCode specifically"

Re: Annoying and alarming things about OpenCode

#118

Post by nylonstrung » Mon, Jul 20, 2026, 2:21 PM UTC

ltbarcly3 wrote: post #97

Opencode's cache hit rate is better than claude code. Opencode has in my experience been better than any of the closed source / closed development alternatives and is not locked down. https://news.ycombinator.com/item?id=48883275

Have you tried Pi though? I was a big Opencode user but once I started using Pi I never looked back

Re: Annoying and alarming things about OpenCode

#119

Post by xg15 » Mon, Jul 20, 2026, 2:22 PM UTC

LaurensBER wrote: post #12

I feel that a better title for this article would be: "Some minor annoyances that, when fixed, would improve OpenCode" # Prompt Cache Misses > It globs your filesystem and re-reads AGENTS.md (injected in turn-0 system prompt) on every SSE turn. If you put a quick note in AGENTS.md to be read in the next session, you immediately force a full re-evaluation. > Personal favourite: it puts the current date in the turn-0 s…

> I feel that a better title for this article would be: "Some minor annoyances that, when fixed, would improve OpenCode"

> If you don’t know what OpenCode is, imagine a boot stamping on a human face forever. The boot is made of TypeScript and the face is everything we have learned about security and systems software since the invention of the electronic computer in the 1940s.

Regardless if that's a good or bad take, I'd like titles on HN to reflect what the author wanted to say and not editorialized to what HN readers think the article should be saying.

Re: Annoying and alarming things about OpenCode

#120

Post by nylonstrung » Mon, Jul 20, 2026, 2:22 PM UTC

mutkach wrote: post #92

Any recommendations for non-typescript-based coding TUI harnesses/agents other than Codex? Given that Codex is open source someone should've built an untethered client?

2 of the most promising Rust ones

https://github.com/1jehuang/jcode https://github.com/gi-dellav/zerostack