dsh-agent-registry

When running multi-agent workflows in DeepSeek Harness, the first real step is anchoring a workspace to an Agent with a stable identity rather than starting from scratch every session. dsh-agent-registry is that first brick in the governance suite: it only registers, explains, and archives — it never intercepts tool calls, so you can build the skeleton before worrying about policy.

Once installed, the session panel gains two tabs: Workspace and Claw. Inside the Claw zone you create Agents by name; each one ships with five configuration facets — Overview, Identity, Model, Permissions, and Skills — and every new session inherits a preset template automatically. Permission entries can be edited and saved per Agent, but the default is enforced: false. Actual policy-based tool gating lives in dsh-agent-gate, a separate plugin in the same suite. Deletion is really an archive of the binding; the project directory and session logs stay on disk.

If you are running collaborative multi-agent work in DSH and want each Agent to carry its own persona and permission boundary without reaching for a heavyweight policy engine on day one, registry is the low-friction starting point. It also serves as the required prerequisite for the rest of dsh-claw-suite — identity injection, policy contracts, session permissions, gate and audit, delegation, and memory — because nothing can be attached before something is registered.