My First Impressions of Deepseek Harness
▲ 80 r/DeepSeekHarness+1 crossposts

My First Impressions of Deepseek Harness

Summary: It’s slow, uses way too many tokens, has a 99% cache hit rate, and gets the maximum performance out of Deepseek.

Performance: Deepseek v4 flash on harness high gave results similar to GPT 5.6-luna low with the same prompt. It was consistent across all my requests (refactoring a form creation system). It followed the patterns and fixed incorrect ones, with no security issues. However, the changes were more about the visual side than backend logic.

Usability: Very confusing. The skills in .agents don’t load automatically, and the documentation doesn’t explain skills in an intuitive way. By default, it’s in Chinese, and you have to click around everywhere to find the English option. The UI looks nice, but it would be better if the default were a CLI. The documentation isn’t clear on how to run it in CLI mode or if that’s even possible.

Strengths: It got the best possible performance out of Deepseek.

Weaknesses: Very slow and used too many tokens (I had to plan on Pi Harness first and then re-plan on Deepseek Harness, which saved about 20M tokens).

There’s a lot of room for improvement. I’ll test its viability and optimizations during the week. The plugin-based system seems like it could be optimized like Pi Harness, but there are so many plugins with no descriptions that it gets confusing.

What has your experience been like? (My context: Typescript + VueJS + QUASAR + HTML, daily use of Pi Harness)

Note: Message translated with Deepseek v4 flash

u/LaxederBR — 6 days ago

I recently did a quick test of Codex, Cursor, and Windsurf, all using the same prompt and file reference. What I noticed was:

Codex (5.4):

- Average speed.

- Did not complete the entire task.

- Did not handle error overflow in a sensitive part of the task.

- VS Code extension not as user-friendly compared to Copilot.

- Did not follow some project standards, such as using softdelete when creating the table.

- Comparison to code produced by Copilot: medium/low.

- Resource consumption: I didn't measure it, I used the free mode.

Windsurf (Kimi 2.5):

- Extremely slow.

- Did not complete the entire task (I stopped after 40 minutes of continuous requests).

- Did not handle error overflow in a sensitive part of the task.

- User-friendly, initial experience close to Copilot.

- Followed project standards.

- Comparison to code produced by Copilot: medium/high.

- Consumption: 10% of the daily quota, 4% of the weekly quota.

Cursor (auto):

- Very fast.

- Completed the entire task.

- Handled an error in a sensitive part of the task.

- Pleasant to use, more cyberpunk experience.

- Did not follow project standards, including migrations, services, and components. The impression on the frontend is of generic output.

- Comparison to code produced by Copilot: low/medium.

- Consumption: I didn't measure it, I used the free mode.

In summary:

- Windsurf proved to be very powerful but unusable.

- Codex and Cursor are a cheaper alternative but require more attention to the code produced.

They all seem to tell you: This plan is just a paid trial, buy the most expensive one and you'll have the full experience.

In my workflow, even if I pay 4x now for Copilot, it will still be worth it. But I feel frustrated; it seems the only way is to spend a good portion of my income doing what I used to do, but in half the time.

I've heard of OpenCode Go, I'll test it, but without much hope.

Running locally on a 6GB VRAM card? It works, but it's useless due to the slow speed and incorrect code.

If anyone has suggestions on what to test, feel free to share them. I'm hyper-focused on finding a solution (like a good developer xD).

reddit.com
u/LaxederBR — 4 months ago