Introduction

DeepSeek Harness (DSH) provides a complete set of agent development capabilities, including persistent sessions, model adaptation, and tool calling. In the Cordis plugin ecosystem, directly adopting these capabilities typically requires manually handling lifecycle management and dependency injection. dsh-cordis packages the DSH coding engine as a standard Cordis plugin, allowing it to be mounted into the caller’s existing Loader tree and solving the problem of integration complexity.

What It Is

dsh-cordis is a package that bundles the DeepSeek Harness coding engine into a Cordis plugin.

  • Maintainer: cordisplugins
  • Core value: Mounts the DSH foundation composition into the caller’s existing Loader tree and provides out-of-the-box DSH capabilities.
  • Type: Client

Core Features

This plugin includes the following capabilities:

  • Composition mounting: Mounts the DSH base composition (including native agents, persistent sessions, model adapters, tools, objectives, planning mode, approvals, and packaged agent presets) into the caller’s Loader tree.
  • Native services: Provides native DSH service providers rather than a global singleton.
  • Service injection: Allows callers to consume it by injecting specific services (such as sessions, agents, or tools) instead of directly importing implementations.

Installation and Enablement

Install the dependency using pnpm:

pnpm add dsh-cordis @deepseek-ai/cordis@4.0.1

Typical Usage

In the host configuration file, use a stable Loader entry to include the plugin. telemetry defaults to false.

- id: dsh-engine
  name: dsh-cordis
  config:
    telemetry: false

Architecture and Considerations

Lifecycle and Ownership

  • No independent root: The plugin does not create another Cordis root.
  • Fiber ownership: Its Fiber owns the enclosed DSH tree. Removing the Loader entry removes its active services and puts consumers into the PENDING state until another provider becomes available.
  • Dependency inversion: Consumers request service contracts such as sessions, agents, and tools, without importing specific DSH providers.

Responsibility Split

  • Host responsibilities: Configuring DSH_HOME, credentials, model selection, UI, and the ACRYL engine selection contract is the host’s responsibility.
  • Telemetry: Disabled by default.

Limitations

  • No Pi integration is provided.
  • No engine switching command is provided.
  • No cross-engine session translation is provided.

Use Cases

Suitable for developers who need to reuse DSH coding engine capabilities within the Cordis plugin ecosystem. It encapsulates DSH’s complex internal implementation inside the plugin and exposes standard Cordis service interfaces externally, reducing the integration cost for host projects.