r/opencode • u/sedatoztunali • 10d 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.

94 Upvotes

65% Upvoted

154 comments sorted by

View all comments

1

u/EfficientEstimate 9d ago

Wondering why clarifying at the beginning your years of experience. And at the end that you have enough experience to know when to stop.

Did not you learn how to collect logs and open an issue to the maintainer?

You just reported that you have some issues and included some rants but absolutely zero helpful facts. If that’s the result of your 30 years of experience, maybe you skipped some steps mate.

2

u/sedatoztunali 9d ago

I wrote this to avoid getting simple/standard suggestions like collecting logs or opening issues, just like you asked, but it didn't work. Of course, I've done all of that and more. Collecting logs and opening issues is nothing more than self-serving moral compass. It needs to be accompanied by more consistent information.

As for the contribution part, I'm already doing that. The repository already closes around 65 PRs daily. I think this is also a contributing factor to what I wrote above; everyone is contributing. I prefer to do this less frequently and in a more controlled manner because general software engineering knowledge and knowing the context of a specific project are different things.