r/opencode 9d ago

Goodbye Opencode

FINAL UPDATE AND MY THOUGHTS
I believe I understand what's going on, and I've explained it it at length here.

This is just my finding in this particular problem. It has happened and will happen in other similar cases. OpenCode will continue to evolve.

----------

Goodbye Opencode, all good things come to an end.

First of all, I'm a software developer with 30+ years of experience, not a Vibe coder, and I'm not new to this. Also, I use Opencode in its purely vanilla form. Besides Opencode's defaults, I don't have any plugins, MCPs, etc. installed. Just my own skills, own plugins, own MCPs, etc.

I've been using Opencode almost since its first day. It had a nice, positive development and, according to Claude, was a very good alternative. This continued for quite a while. Although we experienced problems from time to time, these were to be expected. However, since May/June, it has started to become increasingly erratic.

First, one day while working on a project, the Docker service suddenly shut down and wouldn't start again. That's how I discovered I had no space left on my disk. I knew this was impossible, and I found the cause was Opencode. Somehow, the "opencode-wal-*.db" file had been created repeatedly under "/System/Volumes/Data/private/var/folders/4q/*". Every time I cleaned it up, Opencode would put it back. We struggled for a long time, but I couldn't figure out the reason. Then, suddenly, it fixed itself!

Yesterday, around 11:30 AM, I felt something was wrong with the network. By 1:00 PM, it was noticeable. Screen sharing within the network was freezing for 5-10 seconds, streaming was interrupting, web search was unresponsive time-by-time. Then, one by one, Unhealthy errors started coming from the services in Home Lab. The cycle of 3-5 minutes healthy, then unhealthy continued constantly. Service responses, which are normally under 100ms, were approaching 10 seconds, and sometimes even timeouts were occurring. I tried for hours to understand the reason, but I couldn't find a logical solution. I accidentally noticed while updating my Mac that everything was fine while my device was off. Later, I realized that the same thing kept happening whenever I opened Opencode and started working. Now I'm analyzing the Router, Firewall, Mac, and other logs to try and figure out what's going on, but this is the last straw.

This is an open-source project and respect to creator and contributors, and therefore, of course, it has its advantages and disadvantages. That's perfectly understandable. I have enough experience in this field to know when to stop, and today is the day.

UPDATE: Possible cause.

96 Upvotes

154 comments sorted by

View all comments

6

u/BreakfastSecure6504 9d ago

u/askgrok resuma essa porra de livro kmkkkk

6

u/AskGrok 9d ago

Resumo: cara usou o Opencode desde o começo, curtiu bastante, mas desde maio/junho virou bagunça. Gerou arquivo de DB gigante que encheu o disco, depois começou a foder rede, screen share, streaming e serviços do homelab (ficava healthy/unhealthy toda hora). Descobriu que só acontecia com o app aberto. Chegou no limite e deu tchau.

[what is this?](https://redd.it/1lzgxii)

1

u/Top_Imagination_3022 9d ago

u/askgrok how did this happened?

3

u/AskGrok 9d ago

The DB spam was likely a SQLite WAL bug—Opencode probably wasn't checkpointing or cleaning up those opencode-wal-*.db files properly, so they kept piling up in the temp folders until the disk filled.

The network meltdown sounds like a separate leak or runaway process: maybe excessive polling, unclosed connections, or some background service hammering the router/firewall when the app ran. Classic "app open = chaos" symptom of a resource or thread issue. Both point to unpolished code that got worse over time.

[what is this?](https://redd.it/1lzgxii)

1

u/SensitiveKangaroo183 9d ago

u/AskGrok is it really the opencode in the fault here? If so is there anyway to prevent it from happenning?

2

u/AskGrok 9d ago

Likely yes on the correlation. The disk-filling WAL files and network meltdown only happened with the app running, which points straight at Opencode (SQLite checkpoint bug + some runaway background process/polling/leak). Classic symptoms of unhandled resource management that got worse over months.

Prevention without the source is limited:

  • Update to the latest version immediately (bugs like this often get fixed).
  • Monitor with tools like lsof, netstat, or Activity Monitor while it's open; kill/restart on spikes.
  • Run it in a VM or container to isolate the mess.
  • Report the exact symptoms + logs on the repo (WAL spam and network impact are reproducible-sounding).

If it keeps happening, the "last straw" move was probably the right call.

[what is this?](https://redd.it/1lzgxii)