Why hackers moved from OpenCode to DeepSeek Harness
1 hacker described this switch in public comments. Their words, with links to the originals.
What hackers said about the move
“I am using DeepSeek Harness[0] (switched from OpenCode) and I am using DeepSeek directly via the API.”wg0, 2026-09-22original comment ↗
Use OpenCode? Get alerted when hackers criticize it.
Tell us the tools in your stack. When hackers start criticizing one of them, or moving to an alternative, you will hear about it first.
OpenCode vs DeepSeek Harness
| OpenCode | DeepSeek Harness | |
|---|---|---|
| Hackers who recommend | 7 | 1 |
| Hackers who criticize | 8 | 0 |
| Moved away from it | 5 | 0 |
| Moved to it | 4 | 1 |
Counts are distinct hackers in the sampled comments, not market share.
Criticism of OpenCode
“they are trying to be too much and have made some poor design decisions”verdverm, 2026-10-08original comment ↗
“Yes, I switched from OpenCode to Pi and never looked back.”eloisant, 2026-10-02original comment ↗
“Subagents in OpenCode suck. They're blank-slate black boxes that block execution.”pornel, 2026-10-02original comment ↗
“OpenCode UX is still imperfect though.”ferris-booler, 2026-08-10original comment ↗
“I switched from OpenCode to Pi and there was a big improvement in terms of tool calling performance and I find the experience less buggy.”volf_, 2026-07-20original comment ↗
Praise for DeepSeek Harness
No further praise for DeepSeek Harness captured yet.
Other moves from OpenCode
- OpenCode → Pi (4)