Architecture and plugin ecosystem
A structured comparison of Codex and DeepSeek Harness across runtime architecture, product integration, and extension models, followed by a capability map of both plugin ecosystems based on the official Codex Use Cases.
Architecture comparison
Codex and DeepSeek Harness both manage context, tools, and task execution. Their primary differences lie in runtime composition, product integration protocols, and extension boundaries.
Plugin capability comparison
The nine official capability axes, including Engineering, Front-end, and Automation, provide a consistent index for comparing supported tasks across Codex and DSH. A plugin may map to several axes, so grouped totals differ from deduplicated catalog totals.
Build, debug, deploy, and maintain real software systems.
Evaluate outputs, run checks, and compare implementation quality.
Interfaces, design, visual evidence, and user-experience implementation.
Testing, code review, security checks, and delivery quality control.
Research, scholarly sources, life sciences, and reviewable analysis.
Turn recurring tasks, schedules, and multi-step execution into workflows.
Query, analyze, transform, and present structured or unstructured data.
Connect external services, MCP, APIs, messaging channels, and developer platforms.
Work across documents, communication, research, planning, and team knowledge.
DSH-native capabilities
These plugin families are shaped by the DeepSeek Harness host model, local workflows, and regional ecosystems. No same-position entries were identified in the default Codex directory.
Lark, WeChat, DingTalk, QQ, and related channels form a distinct DSH plugin family.
Themes, skins, wallpapers, sidebars, pets, and workbenches directly extend the DSH host UI.
Cordis, profiles, agent loops, model providers, and subscription bridges extend the DSH host itself.
Marketplaces, installers, health checks, updates, and rollback tools manage the DSH plugin lifecycle.
Desktop apps, launchers, TUIs, tray apps, and LAN access extend local DSH environments.
Codex entries come from the 2026-08-21 official default-marketplace snapshot and use the official Codex Use Cases. DSH entries come from the current public catalog and show a single verification status.
Compatibility boundary
A shared Use Case indicates comparable task goals and supports functional evaluation.
The directory consistently marks entries as Verified or Unverified to distinguish review outcomes.
Installation steps follow the upstream repository instructions; the directory does not host one-click installation flows.