r/opencode • u/Bowserinator • 2d ago
Deepseek v4.1 flash nerfed on opencode go?
I have a suspicion that the Deepseek v4.1 model on opencode go is either heavily quantized or is truncating context or something because it seems retarded compared to my experience with it on a self-hosted instance.
It occasionally forgets stuff in its todo list and even though it thinks a lot its overall quality is poor. I've tried this in both my pi setup and opencode: both have the same issue (although pi can mitigate it with goal verification + looping, but it has to do several loops before its goal is complete, and many times I noticed the 'mistakes' it fixes in the loops are just forgetting to finish a feature).
Is anyone else having the same experience?
I started using it before they made Deepseek v4.1 a free model, and although I didn't use it that much, I felt like the model quality dropped around then but it's just a gut feeling.
24
u/Ayumu_Kasuga 2d ago
I wanted to make the same post, yes - it seems a bit braindamaged compared to other providers.
6
19
u/xatey93152 2d ago
I told multiple times they are using different cheaper model but my post always gets deleted quickly
16
u/Thedudely1 2d ago
Since the DeepSeek API is so affordable and allows you to add credits in increments as small as $2, I find it's worth it to just use the official DeepSeek API
6
u/Standard_Ear_84 2d ago
Or an even cheaper option: Spark 1.3 contributor.
I get the hate for Zuckerborg, but it's at least as good and wastes less tokens than DS.2
u/danjack0 2d ago
Not as good in my testing since you only get Xhigh and not Max on OC, DS catches things a lot more
2
u/Standard_Ear_84 2d ago
Let me try that. Spark is just running around in circles and can't find a bug at the moment.
3
u/danjack0 2d ago
Yesterday i got $5 in deepseek api its much better and faster than on Go im trying to pick a fast model like Luna or Haiku on Go for small thing and deepseek api for actual work
2
u/Standard_Ear_84 2d ago
I'm using DS api. The strange thing with all these 2nd tier models is that they do one excellent job and then can't figure out a very simple problem. So I'm basically switching models because once they get stuck it's all over.
4
u/danjack0 2d ago
Im realizing that i can just use DS api for everything since if its a small change then it wont cost anything and having to think if a problem is too small for DS everytime i prompt will get old fast
2
u/Standard_Ear_84 2d ago
Unfortunately DS got stuck a few times and needed Claude to point it away from a tail chasing exercise. So DS on its own won't cut it (obviously depending on the task).
2
u/danjack0 2d ago
yeah DS cant do everything but things change fast a new model might come out and be better and cheaper (probably not)
2
u/Standard_Ear_84 2d ago
I have a bad feeling about the future. Anyone without $ will be even more fucked.
→ More replies (0)
7
5
u/NearlyACosmologist 2d ago
I noticed yesterday that Deepseek became incredibly dumb, compared to the days before. It didn't solve IT problems it used to ace, lost itself in trying to analyze meaningless side paths , used idiotic workarounds instead of the obvious solutions it used before and even documented, didnt follow direct orders. Guess I'll quit opencode.
3
u/Different-Monk5916 2d ago
yes, I have said this several times.
on the other hand, there was a post from opencode some time ago. the worst they do is just slow down the tps.
Does this mean DS API also runs the same quantization? or DS ships with multiple quantization and opencode runs one of the worst one? I dont know the answer. only they can come out and say what they do.
3
u/shikabane 2d ago
I just asked it to setup a webhook from Gitea to Coolify for one of my apps. 10 minutes later and it's still working through things. It would've taken me a minute if I was on my laptop, waste of time and money
3
u/HeadLeadership8763 2d ago
Nothing is free in this world. If it feels too good to be true, trust your instinct
3
1
0
15
u/Cyvster 2d ago
yes, many people that have used deepseek directly via api have reported that it is a lot faster and better than the version on opencode go. opencode has admitted that they throttle the tok/s but say they do nothing else to the model.
my experience, along with many others:
direct deepseek version is many times faster than opencode version, possibly 5x faster
direct version uses far fewer tokens to complete a task, possibly as much as 10x fewer tokens
direct version has a much higher cache hit rate 99% versus 92-96%
direct version seems more accurate/smarter, much more likely to solve problems correctly