dsh-control-plane

Developers who juggle multiple DeepSeek Harness environments—an official runtime, a team-customized one, a development fork, and separate Agent Presets for different workflows—frequently struggle with a practical problem: each environment carries its own configuration files, session data, and local paths, and switching between them manually is both tedious and error-prone. dsh-control-plane is a local-first developer control plane that unifies these runtimes under a single discoverable catalogue, so you can compose, inspect, and recover them without ever mixing or uploading private files.

Its core capabilities revolve around allowlisted adapters: register any number of DSH runtimes, start, stop, and health-check them through a controlled interface, and connect sessions to plans, artifacts, and knowledge references—all without copying private configuration. The plugin projects read-only panels for the Runtime Catalog, Session Board, Plan Panel, Artifact Board, and Knowledge References directly inside the DSH Web UI, and ships replaceable scenario adapters (such as an interview-learning example) for workflow extension. Web panels are strictly read-only mirrors; actual runtime control stays in the source Runtime Manager API, and the Stage 4 bridge resolves only bounded metadata and opaque references, never document content.

Rather than replacing DSH, dsh-control-plane injects its control-plane capability into your existing workflow as a versioned, installable DSH Bundle. It is designed for solo developers and small teams who switch among several DSH environments regularly and want a unified, auditable view. The repository contains no credentials, raw chats, real sessions, or production configuration; machine-local values live in an ignored local.toml, and all public examples use placeholders and synthetic identifiers exclusively.