Introduction

DeepSeek Harness (DSH) developers often face the challenge of managing multiple environments: official runtimes, team-customized runtimes, development forks, and different Agent Presets can be mixed together, making it difficult to distinguish configuration files and session data and easy to cause environment confusion. dsh-control-plane is a local-first developer control plane designed for this purpose.

What Is This

This is a plugin maintained by Harzva, intended to provide DSH with a stable core for composing, inspecting, and managing multiple runtimes, configurations, sessions, and knowledge references. It does not replace DSH itself; rather, it provides a control plane core and a versioned DSH Bundle that can present this control plane inside DSH.

Core Features

Below are the main capabilities of this plugin:

  1. Multi-runtime registration and management: Supports registering official, team-customized, development, and user-defined DSH runtimes.
  2. Security checks: Can inspect Profile and Preset references without duplicating private configurations.
  3. Runtime operations: Starts, stops, and performs health checks on runtimes through allowlisted adapters.
  4. Session association: Associates Sessions with plans, artifacts, and knowledge references.
  5. Integration panels: Provides additive DSH Host/Client integration panels.
  6. Web visualization: Displays read-only projections of Runtime Catalog, Session Board, Plan Panel, Artifact Board, and Knowledge References in DSH Web.
  7. Scenario adapters: Uses and extends replaceable scenario adapters, including an interview-learning example.
  8. Pre-release validation: Validates release versions using isolated DSH Profiles before publishing.

Architecture and Integration

The current development target of this plugin is DSH 0.1.0-rc.8. The root package provides a dsh.bundle patch layer, a strict ./typert Host manifest, and a preset ./client Bundle. Internal source modules are composed into this installable package, ensuring that the tarball does not depend on sibling file: packages. The Web panel uses additive setup slots and local failure boundaries.

It is important to clarify:
* The Web panel is a read-only projection.
* The behavior of runtime start/stop and health checks remains in the source Runtime Manager API.
* The Stage 4 bridge only resolves bounded metadata and immutable references; it does not read or upload document content.

Development and Build

This repository has completed Stage 7 and published the first public version v0.1.0. If you need to build or validate a candidate version, you can use the following commands:

pnpm install --frozen-lockfile
pnpm run build:dsh
pnpm run check
pnpm run pack:dsh
pnpm run verify:release-candidate

Security and Content

This is a public repository, containing public schemas, adapters, examples, tests, and documentation. It does not contain credentials, raw chat logs, real sessions, private knowledge, private machine paths, or production DSH configurations.

  • Machine-local values should be placed in the ignored agentworkos.local.toml file.
  • Public examples use placeholders and synthetic identifiers.

Notes

  1. Environment restrictions: Developers should use isolated DSH Profiles for runtime inspection. Do not install this directory or locally configured Profiles into production workspaces.
  2. Submission status: Submissions to awesome-dsh-plugin are currently the next stage and have not yet been declared merged or accepted.

Conclusion

dsh-control-plane provides DSH developers with a decoupled approach to managing multiple environments and configurations locally. Through read-only projections and isolated validation, it reduces the complexity and risk of environment management.