ZSeven-W/dsh-crew
Dispatch work to DeepSeek Harness agents from Claude Code, Codex, Antigravity or Grok while keeping the host's native subagent UI.
DSH Crew makes DSH agents dispatchable from Claude Code, Codex, Antigravity and Grok while keeping the host's own native subagent UI: the orchestrator keeps its model, the work runs on a real DSH agent with that harness's tools, sandbox, presets and session history, and the host still shows it as a native subagent with live progress. Tiers (flash / pro) select capability from DSH's configured model roster, and tier_policy can clamp every dispatch to one tier while escalate_on_failure retries a failed flash run once on pro. A jobs board lists running and finished worker jobs with tier, effort, live progress and tokens, held workspaces name their holders, and a job that vanishes mid-flight (e.g. a hub restart) surfaces as an orphan ghost. Dispatch guardrails cap worker→worker nesting at origin-chain depth 3, refuse cycles and refuse a second worker on a held workspace. Because DSH models are text-only, describe_image and generate_image source vision and image generation from DeepSeek's own VL model or the CLIs you already have, and pasted images reach the model as transcribed text. One-click install wires up each host's marketplace registration, permission allowlist and HUD statusline segment.
Install
dsh plugin --profile web add @zseven-w/dsh-crew@latestCopied verbatim from the README's 'Install' section, which installs the plugin into a DSH profile from npm and then runs dsh web. The README offers a local-development alternative, dsh plugin --profile web add link:/path/to/dsh-crew, which symlinks the profile dependency to the source tree. In hub mode workers reuse the DSH instance's existing DeepSeek credentials; only the standalone fallback needs a DEEPSEEK_API_KEY written to ~/.config/dsh-crew/.env.
Compatibility
DeepSeek Harness. Installs as a standard DSH bundle (dsh.bundle + cordis.patch.yml) into a web profile, where worker sessions become first-class DSH sessions; without DSH running it falls back to a standalone DSH runtime for CI/headless use. It also runs as an MCP service dispatched from Claude Code, Codex, Antigravity and Grok. Runtime dependencies are only @modelcontextprotocol/sdk and zod; every @deepseek-ai/* package is host runtime provided by the DSH host. No Node range is stated; the README documents a pnpm install development flow.
Details
- Repo: ZSeven-W/dsh-crew
- Category: Agent Capabilities
- Stars: 156
- Version: GitHub repo ZSeven-W/dsh-crew; npm package @zseven-w/dsh-crew, current plugin release 0.1.0-rc.11, tested with DSH 0.1.1-rc.1; MIT
FAQ
- Which host agents can dispatch DSH workers?
- Claude Code, Codex, Antigravity (agy) and Grok. Each has a one-click installer (Settings → DSH Crew) or a CLI command such as node src/install/cli.mjs all; restart the session after installation for changes to take effect.
- What happens if DSH Web is not running?
- The hosts' MCP shim auto-detects the hub (default http://127.0.0.1:3080). If DSH Web is running, jobs enter hub mode as sessions inside DSH; otherwise dispatch falls back to a standalone DSH runtime (dsh-jsonrpc-agent), which is what CI and headless environments use — and that path needs its own DEEPSEEK_API_KEY.
- How are runaway recursive worker dispatches prevented?
- Every dispatch is checked before anything spawns: the worker→worker origin chain is capped at origin_depth_limit (default 3), any cycle (the same backend + cwd appearing twice) is refused, and a second dispatch into a workspace already held by a running worker is refused with the holder's job id, backend and start time unless allow_concurrent_cwd: true is passed for read-only tasks.
Alternatives
PerryLink/dsh-background-agents · lynx-gt/dsh-subagent-cwd · MiloMMIN/dsh-agent-board