跪拜 Guibai
← All articles
Backend · Programmer · Artificial Intelligence

DeepSeek Harness Ships as a Bare WebUI — the Community Built the IDE Around It

By cxuanAI ·
Read original on juejin.cn ↗ Google Translate ↗ Alt translation

The Harness launch is a live experiment in whether an AI coding platform can succeed by shipping only the model runtime and a plugin protocol, leaving every interface decision to third parties. If Cordis stabilizes and the tooling matures, DeepSeek could become the VS Code of agentic coding — a thin official core with a community-owned surface. If the plugin APIs fragment or the ecosystem stalls at novelty skins, the project collapses under its own open-endedness.

Summary

DeepSeek Harness arrived as little more than a WebUI shell, deliberately leaving the interface layer to its Cordis plugin system. The community responded immediately. dsh-better-sidebar adds a Codex-like workspace with file editing, terminal, and Git tabs. dsh-TUI pulls the entire interaction into a terminal session for developers who live in the command line. deepseek-harness-desktop wraps everything in an Electron app with system-tray integration — no Node.js or CLI commands required.

Vision and multimodal support, which DeepSeek's own API lacks, arrived through dsh-vision-toolkit (external API key) and dsh-vision-proxy (local Ollama fallback). Memory plugins like dsh-mnemon and distill layer on long-term recall and automatic skill distillation. Scheduled task runners, multi-agent workflow orchestrators, and a database agent round out the serious tooling. A plugin marketplace already indexes over 300 extensions.

Not everything is productive. A wave of anime-themed skins and desktop pets — built by the same ACM gold medalists recruited during the closed beta — has drawn sharp criticism for squandering talent on cosmetic fluff. The community's verdict, quoted in the piece: "Between 'so awesome' and 'so fun,' they chose 'so fun.'"

Takeaways
— DeepSeek Harness ships as a bare WebUI; all CLI, TUI, and desktop interfaces come from community plugins built on the Cordis system.
— dsh-better-sidebar adds a Codex-style workspace with file browsing, terminal, Git, and extensible tabs directly inside the WebUI.
— dsh-TUI moves the entire interaction into a terminal session, covering all common commands for developers who prefer CLI workflows.
— deepseek-harness-desktop is an Electron wrapper that auto-starts the local Harness service and requires no Node.js or command-line setup.
— dsh-at-file enables @-mention file referencing for editing, replicating a feature familiar from Codex.
— Vision plugins fill a gap in DeepSeek's API: dsh-vision-toolkit uses an external vision model API key, while dsh-vision-proxy falls back to a local Ollama instance.
— dsh-mnemon implements a three-tier local memory system (hot, project, long-term) stored in SQLite, JSON, and Markdown, shareable across agents.
— distill runs background subagent reflection and automatically distills experience into reusable skills.
— dsh-automation schedules coding tasks in fresh sessions with restricted permissions; operations needing manual approval fail instead of blocking.
— dsh-workflow adds persistent multi-agent orchestration with save, govern, and recover capabilities for repeated processes like code review and parallel research.
— dsh-data-agent connects to MySQL, PostgreSQL, SQLite, Oracle, Hive, and Impala, but auto-commits write operations — a risk worth noting.
— dsh-market is a VS Code-style plugin marketplace already listing over 300 extensions with in-UI search, install, update, and uninstall.
— A wave of anime skins and desktop pets from the closed-beta cohort drew criticism for wasting ACM-level talent on cosmetic plugins.
Conclusions

Shipping only a WebUI and a plugin protocol is a deliberate architectural bet: it treats TUI, desktop, and even vision as "visual plugins" the community should supply, keeping the official surface minimal.

The speed of community response — TUI, desktop, vision, memory, and workflows in days — validates the plugin-first approach but also exposes how much was missing at launch.

The criticism over ACM gold medalists building anime skins points to a real tension: recruiting elite talent for a platform that then channels effort into novelty plugins signals either poor direction or a deliberate strategy to generate viral attention.

Long-term viability hinges on Cordis API stability, plugin governance, and developer tooling — documentation, scaffolding, debugging, and distribution — not on how many plugins appear in the first week.

The comparison to VS Code is apt but loaded: VS Code succeeded because Microsoft invested heavily in the extension API and marketplace infrastructure, not just because it was extensible.

Concepts & terms
Cordis plugin system
The extension framework underlying DeepSeek Harness. It allows third-party developers to build plugins that modify or replace the interface, add tooling, and integrate external services, treating everything from TUI to desktop as a plugin.
dsh-mnemon three-tier memory
A local memory architecture splitting agent context into hot memory (current turn), project files (full read), and long-term memory (on-demand recall), stored in SQLite, JSON, and Markdown and shareable across agents that connect to the same Mnemon service.
dsh-automation session isolation
Scheduled tasks run in fresh sessions without inheriting prior approvals or context. Permissions are limited to read-only or workspace writes; any operation requiring manual approval fails immediately rather than blocking.
Source: juejin.cn ↗ Google Translate ↗ Backup ↗