I've gotten a lot of good work done with deepseek models. Like with any generic harness there's some tuning that has to happen. I used open code for a while, but I've landed on pi.dev as my go to since its easier to tune and has better deepseek integration. iirc open code is quite bad at utilizing cache and doesn't have a lot of ways to specifically tune the harness for a particular model.
replyI've found it to be pretty good so far.
reply(1) you used opencode
(2) what provider did you use. openrouter is trash because they shit up the model serving. no max effort and horrific cache utilization, on the order of 50-75%, absolutely garbage. beware
replyWhat should we be running deepseek on besides opencode? I chose it because I heard good things. Also provider is directly through deepseek credits.
replyI use the Deepseek API and pay peanuts. Very satisfied.
replyoh you used opencode go?
replyharness: omp.sh
[dead]
replyYou're mad.
replyPoint 1 finger out, and you point 4 back.
replySaid the man with 6 fingers.
reply