Just tested through openrouter.. gave exactly same task.. the task was to scan existing repo, and generate a single docker-compose file to deploy behind a caddy server, where certain port ranges are already used, the service demands widlcard certificates to be provisioned from outside, and postgre needs to be built-in one... Tested this model, and gpt-5.6-terra-high. Results: this one had few issues. terra: none. The…
What harness are you using? DS V4 is harness sensitive.
DeepSeek V4 Pro 0813
131–140 of 493 posts
Re: DeepSeek V4 Pro 0813
#132Re: DeepSeek V4 Pro 0813
#133Earlier quoted context omitted.
wait for Deepseek Harness (yes it is the official name) release then try again. for your kind of task, harness tools matter.
If the model cannot figure out simple and ubiquitous tools, how is it supposed to figure out complex problems? All of the good models basically work with any harness, including giving them a single "shell command" tool. They can just figure things out.
I get drastically different tool call failure rates using Claude SDK vs OpenCode using Qwen 3.6 models
Re: DeepSeek V4 Pro 0813
#134Earlier quoted context omitted.
wait for Deepseek Harness (yes it is the official name) release then try again. for your kind of task, harness tools matter.
If the model cannot figure out simple and ubiquitous tools, how is it supposed to figure out complex problems? All of the good models basically work with any harness, including giving them a single "shell command" tool. They can just figure things out.
Re: DeepSeek V4 Pro 0813
#135Earlier quoted context omitted.
If the model cannot figure out simple and ubiquitous tools, how is it supposed to figure out complex problems? All of the good models basically work with any harness, including giving them a single "shell command" tool. They can just figure things out.
When it comes to quality of outcome, since at least Feburary, the harness has almost equal, if not more weight than the model itself. It's no longer "which model is the best?" it's "which model + harness is the best?" I get drastically different tool call failure rates using Claude SDK vs OpenCode using Qwen 3.6 models
Re: DeepSeek V4 Pro 0813
#136Re: DeepSeek V4 Pro 0813
#137Re: DeepSeek V4 Pro 0813
#138Earlier quoted context omitted.
If the model cannot figure out simple and ubiquitous tools, how is it supposed to figure out complex problems? All of the good models basically work with any harness, including giving them a single "shell command" tool. They can just figure things out.
When it comes to quality of outcome, since at least Feburary, the harness has almost equal, if not more weight than the model itself. It's no longer "which model is the best?" it's "which model + harness is the best?" I get drastically different tool call failure rates using Claude SDK vs OpenCode using Qwen 3.6 models
This feels like a horrible failing of the models to generalize, then - both basic and intermediate tasks should be possible to do with Claude Code, OpenCode, Pi, ZCode, Kimi Code, Dirac and tbh any other mainstream or even slightly niche harness. Not doubting the claim itself, there's a reason why good benchmarks include the harness.
Re: DeepSeek V4 Pro 0813
#139Earlier quoted context omitted.
wait for Deepseek Harness (yes it is the official name) release then try again. for your kind of task, harness tools matter.
If the model cannot figure out simple and ubiquitous tools, how is it supposed to figure out complex problems? All of the good models basically work with any harness, including giving them a single "shell command" tool. They can just figure things out.
also, even if some models claim that they have full 1M context window, some only work effective with the head or tail of the window, a proper harness tool will know about the limitation of the model and act accordingly.
then also the output format, the tool calling syntax, the quirks and gotchas of each model.
it is not simple as just throwing everything at the model, especially when your project has hundred of files or so.
Re: DeepSeek V4 Pro 0813
#140Earlier quoted context omitted.
If the model cannot figure out simple and ubiquitous tools, how is it supposed to figure out complex problems? All of the good models basically work with any harness, including giving them a single "shell command" tool. They can just figure things out.
When it comes to quality of outcome, since at least Feburary, the harness has almost equal, if not more weight than the model itself. It's no longer "which model is the best?" it's "which model + harness is the best?" I get drastically different tool call failure rates using Claude SDK vs OpenCode using Qwen 3.6 models