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

21–30 of 309 posts

Re: Annoying and alarming things about OpenCode

#21

Post by dv_dt »

awinter-py wrote: post #14
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

yeah I noticed it missing on the openrouter leaderboard -- very interested to know what that's about

probably about their own model routing service zen?

Re: Annoying and alarming things about OpenCode

#23

Post by nextaccountic »

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"

Those are labeled as "annoying things"

Read also the "alarming things"

Re: Annoying and alarming things about OpenCode

#24

Post by alanwreath »

I’m not really here to defend opencode (or bash it, who has the time?), but in setting up SDD paired with the right tools to both make deterministic black boxes out of certain actions, paired with subagents. I have ran with opencode and qwen 3.2 on a 5090 and I’m getting results on a production codebase of golang where a review of changes from Claude had no changes but acceptance of the solution.

I may be missing some aspect of where the local llm’s are losing, but I’m content with draining my local tokens and treating the frontier models like a less junior SWE.

Re: Annoying and alarming things about OpenCode

#25

Post by nthypes »

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

How you deal with LSP? One of the best things in OpenCode is LSP integration.

Re: Annoying and alarming things about OpenCode

#27

Post by wren6991 »

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.

Re: Annoying and alarming things about OpenCode

#30

Post by urvader »

About the caching things. This is a flaw in the backend, not in the Frontend. If the backend is only relying on prefix cache you need to look for more fine grained cache solutions like HiCache or Lmcache. If your backend discards the whole cache because of one date is changed, you really can’t blame it on the Frontend. It is an implementation detail that you push to the wrong side.
Post reply on HN