DSH Crew
A Crew orchestration plugin for the official DeepSeek Harness. It adds
Worker/Reviewer dispatch, model priorities, job tracking, and a capability-aware
safety gate for Codex Desktop, ZCode, and Claude Code.
简体中文
Quick start
Requirements: Windows, Node.js, and Git. Managed 3210 supervision is currently
supported on Windows; Linux and macOS are not yet production runtime targets.
The desktop frontend also requires the separately installed official CLI
(npm install -g @deepseek-ai/dsh@latest, providing dsh.cmd on PATH).
npm install -g @ran-sh/dsh-crew@latest
dsh-crew install
DSH Crew is installed as a plugin in a dedicated official DeepSeek Harness
profile named dsh-crew, served on 3210. That profile is the canonical Crew
control and execution surface.
The desktop launcher opens the official Harness on 3080 and starts Crew on 3210
with no console window or automatic backend browser tab. Background/login startup
starts only Crew. The official profile is not modified by the Crew installer;
normal official application startup manages its own state.
On Windows, installation registers login startup. To start immediately and
open the Crew control:
& "$env:USERPROFILE\.config\dsh-crew\launchers\start-dsh-crew.cmd" --open
The daily page is http://127.0.0.1:3080/. The backend settings remain available
at http://127.0.0.1:3210/ when explicitly needed. Desktop launch mounts the
simple Crew panel using a Crew-owned --patch overlay, without installing it
into the official profile. Its button opens 3210; the backend button opens 3080.
Install, update, and rollback also converge the Windows watcher automatically:
the exact old watcher is handed off, and completion is reported only after the
new 3210 Crew and DSH versions are verified. No 3080 restart is involved.
dsh-crew status
dsh-crew inspect
Fresh installs contain only the built-in DeepSeek route. Add your own provider
credentials, model priorities, and optional integrations in the local Settings;
they are never bundled into this package.
| Surface | Purpose |
|---|
3080 | Daily official Harness web frontend; opened by the desktop launcher |
3210 | Hidden Crew backend; explicit advanced configuration via its web page |
In Settings → DSH Crew, refresh Harness Models and order the Worker and
Reviewer model lists. Then ask a host agent:
Use ds-worker to implement this change and run its tests.
Use ds-reviewer to review the result.
Codex, ZCode, and Claude use the installed managed integration. The policy
checks live Crew capabilities before dispatch; if a selected Crew capability
becomes unavailable, the host pauses for an operator decision instead of
silently falling back.
Useful commands
dsh-crew inspect # live capabilities and readiness
dsh-crew jobs list # jobs and Result Contracts
dsh-crew providers list # 3210 Harness provider inventory (secret-free)
dsh-crew providers migration-status # detect legacy base providers; no automatic migration
dsh-crew providers migrate-plan <provider>
dsh-crew providers migrate <provider> --plan <id> --confirm # writes user layer, restarts 3210, verifies
dsh-crew providers rollback-migration <provider> --plan <id> --confirm
dsh-crew providers probe <provider-id>
curl http://127.0.0.1:3210/_dsh/dsh-crew/credential-references # references/orphans only
dsh-crew credentials list # secret-free reference inventory
dsh-crew credentials purge-plan env:NAME
dsh-crew credentials purge env:NAME --plan <plan-id> --expected-revision <sha256> --confirm
dsh-crew providers delete-plan <provider-id> --replacement-default <provider-id>
dsh-crew providers delete <provider-id> --plan <plan-id> --expected-revision <sha256> --confirm
dsh-crew releases list # retained validated payloads
dsh-crew rollback <version> # switch payload and verify the 3210 runtime
dsh-crew update # update and repair enabled integrations
dsh-crew uninstall # remove managed files, keep backups/config
The dedicated official Harness runtime state is isolated under
~/.config/dsh-crew/harness with profile: dsh-crew; DSH Crew itself remains a
plugin, not a fork or replacement of DeepSeek Harness. The official web
profile is outside Crew ownership and read-only to Crew; in other words, the
official web profile is never mutated. An old 3080 bridge, if present, is
only reported as a deprecated diagnostic.
Legacy launcher migration
For launchers at <= 0.3.3, refresh the launcher first. The old updater cannot discover newer releases and cannot be retroactively fixed:
npm install -g @ran-sh/dsh-crew@latest
dsh-crew update
Install from source
git clone https://github.com/Ran-sh/dsh-crew.git
cd dsh-crew
node scripts/setup.mjs install
node scripts/setup.mjs status
node scripts/setup.mjs uninstall
Run tests with node --test test/*.test.mjs. See installation,
UI surfaces, readiness,
and job contracts for details.
MIT
