Building AI Agents Like LEGO Bricks: What Changes Can DeepSeek Harness Bring?

Avatar 0

Reported by NUPIAO News | Song Jianan

DeepSeek Harness is finally here—but it’s probably not what everyday users were picturing.

On the evening of August 13, DeepSeek officially released the DeepSeek Harness Developer Preview v0.1, open-sourcing the full codebase under the MIT license. This agent runtime framework, built around the philosophy of “everything is a plugin,” is attempting to rewrite from the ground up how developers around the world build AI agents.

According to the DeepSeek Harness team, it uses a plugin-based open architecture to construct the Agent Harness: every agent capability—models, tools, skills, sessions, sandboxes, storage, loops, scheduling, UI, and more—is assembled from plugins that can be freely swapped out and flexibly recombined.

Let’s break that down. DeepSeek Harness is built on the Cordis plugin system, which is designed for spatiotemporal composability. The Cordis meta-framework only handles plugin loading, unloading, and dependency management—every concrete component of the Agent Harness is just a different Cordis plugin. These plugins collaborate through Cordis services and events, and can be freely combined at the configuration layer.

In plain terms, developers don’t need to modify DeepSeek Harness’s source code at all. They can independently select, replace, or extend any capability via plugins. But for regular users, this isn’t something you can just pick up and use right away.

To handle different use cases, DeepSeek Harness offers four modes, each loading a different default set of plugins. Standard Mode comes with a full toolkit. PTC Mode enables Programmatic Tool Calling, where a single block of code generated by the model orchestrates multi-round tool calls. Minimal Mode keeps just one shell tool and one file editor, designed for benchmarking models in a bare-bones environment. Creator Mode lets you inspect the current runtime, experiment with Cordis plugins in memory, and mix-and-match to create entirely new modes.

If you think of a large language model as a “brain” that only thinks, and an Agent as a complete work unit that thinks, executes, and debugs, then Harness is the central scheduling system that connects the brain to the tools and limbs.

In this “nervous system” built on the Cordis framework, models, command-line tools, file editors, memory storage, and even the UI—all of it becomes pluggable components. Developers don’t need to wade through boring low-level code. They simply tweak configuration files to snap their favorite components together, just like building with LEGO bricks. This design transforms agents from “obedient workers” into a “build-as-you-wish” development framework.

In the past, if you wanted an agent to tackle complex programming tasks, you were often stuck accepting the vendor’s complete package. Models, tools, and sandboxes were locked inside a black box, and changing any tiny detail was a headache.

DeepSeek Harness shatters that status quo. For developers, this isn’t just about freedom—it’s about taking back control. You can swap models on the fly to get the best performance-per-dollar, or write custom plugins to fit your internal coding standards.

Looking at feedback from developers, DeepSeek Harness is offering a genuinely different alternative to Anthropic’s Claude Code. It elevates the competition from “model capability” to the underlying runtime—how models actually use tools.

If you compare the two, Claude Code feels like a polished, plug-and-play commercial product, ideal for enterprise users who prioritize efficiency and trust the official ecosystem. But that closed nature comes at a price.

DeepSeek Harness, on the other hand, is an open “workshop.” Sure, the current preview still needs polish in terms of maturity, but it hands developers nearly unlimited room for secondary development. For teams that want to master the underlying scheduling logic of agents and pursue highly customized deployments, Harness is seriously appealing.

One developer posted on social media: “DeepSeek’s design has a strong LEGO and Minecraft vibe—fully modular. You can rewrite or replace any part you don’t like. It’s completely unlike Codex’s closed black box.”

That developer believes DeepSeek Harness is a truly community-driven product. If it continues to optimize against Codex and Claude Code, it could end up going toe-to-toe with Pi Agent. Pi-Agent is a lightweight AI agent runtime framework initiated by Mario Zechner and maintained by Earendil-Works, also open-sourced under the MIT license.

There are also comments pointing out that DeepSeek only has open weights but no open agent runtime framework, making the product feel like a half-finished job. The plugin-based Cordis is a bold architectural experiment—it lets the community actually extend models’ functionality, not just run them.

Developers generally agree that this “model-agnostic” design direction is an inevitable industry trend. After all, as large model capabilities converge, the new battleground is about building a solid, flexible, and controllable agent runtime at the application layer.

But some developers also warn that the “everything is a plugin” design leans heavily on configuration—YAML files, plugins, effect components, and services. It’s powerful for advanced users, but for anyone who just wants a working agent quickly, the learning curve is steep.

Still, the v0.1 release is just a starting point. The multiple modes it includes already cover scenarios from basic tasks to advanced development. Some tech insiders predict that as sub-agent orchestration, persistent memory, and richer scheduling capabilities are added down the road, DeepSeek Harness has a real shot at becoming the “Linux” of AI agent development—a de facto industry-standard foundation.

DeepSeek is clearly no longer satisfied with just offering a powerful model. It wants to define the “rules” for how agents work. By going open source, it’s rapidly pulling in a global developer ecosystem, using extreme flexibility to challenge the moats of closed-source products. This isn’t just a technical showdown—it’s a battle for control over the AI ecosystem itself.

Advertisement

Leave a Reply

Your email address will not be published. Required fields are marked *

Log In / Sign Up

Enter code for secure login, or use password.

Code Login Password Login