Hubs AI and Technology Post
Join TrustHub to participate — every member is ID-verified
Sign Up Free
0

DeepSeek Is Betting the Harness Matters as Much as the Model

The first time I used Claude models inside OpenClaw, the results were bad.

This was when OpenClaw was still very new. I remember thinking, how can Claude be this capable and still perform this poorly? The model was not the whole problem. The harness around it was.

That was when I started paying attention to something most AI conversations skip. A model can be excellent and still feel useless if the software handling its tools, memory, permissions, context, and work loop is badly designed.

DeepSeek just released a new open-source harness that takes that idea seriously. It is called DeepSeek Harness, and its main argument is simple: everything should be replaceable.

The model is only half the agent

DeepSeek's own description separates the two parts clearly. The model provides the intelligence. The harness lets that intelligence understand an environment, use tools, and keep working through a real task.

That sounds obvious, but most of the products people use do not really work that way. Claude Code is built around Claude. Codex is built around OpenAI's models. OpenClaw could connect to strong models, but that did not guarantee the overall experience would be strong.

The harness decides what the model can see. It decides how tools are presented. It decides what gets remembered, what gets forgotten, how errors are handled, how long the agent keeps trying, and whether you can understand what happened after the run goes wrong.

A powerful model inside a weak harness can look like a weak model.

I learned that from using Claude in OpenClaw. I was not comparing model benchmarks. I was watching the system try to complete real tasks, and the results were disappointing. I could not figure out why it was so bad. Now I understand that the model and the harness were not working well together.

DeepSeek is opening up the missing layer

DeepSeek Harness is in developer preview and released under the MIT license, according to DeepSeek's announcement and its GitHub repository. It is not limited to DeepSeek models. The project documents support for providers including Anthropic, OpenAI, Google, and custom compatible gateways.

The unusual part is how far the plugin idea goes. DeepSeek lists models, tools, skills, sessions, sandboxes, storage, loops, scheduling, and the user interface as replaceable pieces. The New Stack also reported that the model adapter, tool registry, session log, and agent loop can all be swapped out.

That matters because it means the project is not just another coding assistant with a different logo. It is an attempt to make the machinery around the model open as well.

DeepSeek also says every model-visible event is recorded in an append-only session log. That includes system prompts, reasoning, tool calls and results, subagent scheduling, and context added during a run. Resume, fork, search, and replay all work from that same event stream.

That is the kind of feature people usually appreciate only after something breaks. When an agent makes a bad change or gets stuck in a loop, I want to know what it saw and why it made the next decision. “The model messed up” is not enough. Sometimes the model made a reasonable decision with bad context. Sometimes the harness gave it the wrong tools. Sometimes the loop itself was the problem.

Hermes is still my go-to

I have been waiting for someone to build the perfect harness for open-weight models. Hermes has been my go-to so far. It is good, but it still has things to improve. That is not a criticism unique to Hermes. It is the reality of building this category while the models and the tools keep changing underneath it.

What I want is not another closed product that makes one model look good. I want a harness where I can choose the model, change the tools, inspect the run, control the permissions, and keep my sessions usable when I switch providers.

That is why this release interests me more than another model announcement. I do not know if DeepSeek Harness is good yet. I have not had time to try it, but I plan to later today. Open-weight models are getting easier to download, but downloading weights is only the beginning. If the harness is poor, the model will still feel poor. If the harness is good, a model that looked average in a simple chat may become genuinely useful in a real workflow.

The best open model is not always the one with the highest benchmark score. It may be the one that works reliably inside a system you can understand and change.

This is promising, not finished

DeepSeek Harness is not the perfect harness yet. DeepSeek calls it a developer preview, and the repository warns that compatibility-breaking changes are coming. The New Stack also reported that DeepSeek is not accepting outside pull requests right now, directing contributors toward discussions and plugins instead.

Those are real limitations. I would not build a critical production system on an early preview and assume the interfaces will stay stable.

But I do not need it to be finished, or even proven good yet, for the release to be interesting. What catches my attention is that an open-source harness with serious money and a major AI lab behind it is finally entering the conversation. That gives the category more weight than another weekend project, even if the project still has to earn its reputation.

I want more serious open-source competition in this layer. I want Hermes to get better because projects like DeepSeek Harness are making the design space clearer. I want other developers to take the useful parts, reject the bad parts, and build something better.

For a long time, the AI industry treated the harness as a disposable wrapper around the important thing, which was supposed to be the model. My experience with OpenClaw taught me the opposite. The wrapper can decide whether the model is useful at all.

DeepSeek is now betting that the wrapper should be open, modular, and inspectable. I think that is the right direction.

The model gets the headlines. The harness determines whether the headline survives contact with real work.

0 Comments

Log in to join this hub and comment.

No comments yet. Be the first to reply!