dsh-compat

As DeepSeek Harness matures into a next-generation agent workflow engine, many teams still carry a backlog of legacy Claude Code or Codex plugins—Skills, MCP servers, Hook scripts spread across repositories. Rewriting every one from scratch is costly and risks losing the original semantics. dsh-compat bridges that gap: it onboards a legacy plugin as a single lifecycle unit into DSH, preserving the original directory layout, configuration semantics, and operational behavior so nothing has to be redesigned on the DSH side.

Architecturally, dsh-compat separates Source (origin) from Plugin (runtime instance) as two distinct management layers, accepting plugins from Git URLs, local directories, or archive files. A single atomic install covers Skill discovery with dynamic providers, MCP stdio and streamable-http wiring, and Hook parsing with event mapping. Install, enable, update, and rollback all operate as whole-transaction actions—if any target fails, nothing is committed. Administrators can manage everything through the DSH web settings page, or drive the lifecycle programmatically via the ctx.compat service API from other DSH plugins. A built-in diagnostic system surfaces findings at error, warning, and info levels so that compatibility gaps stay transparent rather than silently degrading.

It is well suited for DSH users who want to keep their existing Claude Code or Codex plugin assets productive, particularly when those plugins involve complex Hook orchestration, multiple MCP services, or dynamic Skill Providers. Teams rolling out DSH internally will also find it a useful bridge during the transition window, keeping legacy tooling alive while new-native plugins are being written.