DeepSeek plans official plugin marketplace for Harness, which reaches 1.54 million daily users

The announcement

DeepSeek confirmed it will build an official plugin marketplace for Harness, according to a report by TechNode published on November 6, 2026, based on data from the Chinese portal IT Home. The idea is to centralize the distribution of third-party extensions, currently scattered without a single channel, and make discovery easier for users.

Along with the store, the company is preparing a creator support program that includes token incentives (credits for using the company's own API), direct technical exchanges with the team, and in-platform recommendations. DeepSeek also promises improvements in the stability, compatibility, and security of the plugin API, the three points that historically hold back any extension ecosystem before it matures.

Harness, the product behind the announcement

The report doesn't explain what Harness is beyond usage numbers, which is common in short items from Chinese tech news. But the name isn't random: in AI agent vocabulary, a harness describes the layer that gives a language model the ability to call tools, execute code, and act on external systems, the scaffolding that connects the model to real-world tasks. It's the same logic used in open source coding agents and in model evaluation frameworks.

The existence of a plugin marketplace reinforces this reading: third-party extensions typically serve to expand what an agent can do, such as connecting to a database, calling an external API, or running a system command. In short: everything indicates that Harness is DeepSeek's agent execution layer, accessible through the company's official API, already functioning as a platform open to third-party extensions even without a centralized store.

The numbers behind the move

According to IT Home, cited by TechNode, Harness logged 1.54 million daily active users on November 4, 2026, counting only those who access the service through DeepSeek's official API, meaning total usage could be higher. Third-party plugins already number around 35,000, and roughly 60% of active users have created or installed at least one.

These numbers say two things about the stage of the ecosystem:

• Adoption is already the majority: with 6 in 10 users working with plugins, installing an extension has already become the norm, not the exception, among Harness users.
• Fragmented supply needs order: 35,000 plugins without a central official store tend to mean poor discovery, inconsistent documentation, and duplicated functionality, exactly the problems a marketplace tries to solve.

Why a marketplace, and why now

Centralizing plugin distribution is the classic move for any platform moving from an organic growth phase to a curation phase: VS Code did this with its extensions Marketplace, Chrome with the Web Store, and coding agent tools have been adopting MCP (Model Context Protocol) registries to organize third-party integrations. The difference here is the bet on token incentives for those who create quality plugins, a direct monetization model within the API's own usage ecosystem.

This choice is also strategic for retaining developers: DeepSeek competes for the attention of AI tool builders against providers with already mature plugin and extension ecosystems. A well-designed creator program reduces the friction of contributing and creates a recurring incentive to keep plugins updated, something marketplaces without monetization usually fail to sustain over the long term.

Security is the real concern

Plugin marketplaces have a history of serving as attack vectors when curation is loose. The VS Code Marketplace has already had malicious extensions removed after they ran arbitrary code on users' machines, and npm registers recurring cases of compromised packages distributed as legitimate dependencies. For an agent ecosystem, which by definition executes actions and doesn't just display information, the risk is greater: a malicious plugin could have access to API calls, credentials, and automated actions.

DeepSeek signals it will work on the stability, compatibility, and security of the plugin API, but the source doesn't detail a review mechanism, sandboxing, or permissions policy. This is the point most worth monitoring before any team considers installing third-party plugins in a production environment.

What hasn't been said yet

The source doesn't provide a launch date for the marketplace, curation criteria, or whether the incentive program will have a guaranteed minimum value or will depend on usage metrics. There's also no detail on whether the store will be open to developers outside China or will have language, documentation, or regional verification barriers.

For those who follow DeepSeek's product history, these gaps tend to be filled in subsequent technical announcements, usually via the API changelog or official documentation, not through the press.

What changes for developers in Brazil

Today, DeepSeek's Harness barely registers on the radar of those building AI agents in Brazil, where the dominant ecosystem revolves around MCP (from Claude), OpenAI's function calling, and frameworks like LangChain and CrewAI. An official plugin marketplace only changes this calculation if it comes with two factors the source hasn't yet confirmed: documentation accessible outside Chinese and friction-free registration for developers outside China.

If that happens, the practical appeal is concrete: DeepSeek is already a reference for cost-benefit among open models, and a plugin ecosystem with token incentives lowers the barrier for anyone wanting to test an integration without relying solely on their own application consuming the API. For teams already using DeepSeek models via API in production, it's worth following the company's official changelog in the coming weeks: that's where, not in this note, plugin submission criteria and security policy should appear first.