Runs work as a crew of role agents: a product manager writes the PRD or DoD, waits for your confirmation, then starts architect, engineer, QA and reviewers whose tool sets are locked per role, and shares work through files on disk.
Install
# from npm (prebuilt)
dsh plugin --profile web add dsh-crew
# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)
dsh plugin --profile web add github:stuarthu/dsh-crew
Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).
README
Version 0.9.0.
dsh-crew is a plugin for DeepSeek Harness (dsh). It turns your dsh session into a product manager (PM) that runs a crew of role agents: architect, engineer, test engineer, code engineer, QA, code reviewer, security reviewer, doc reviewer, and researcher.
What it is
You talk to the PM. The PM starts role agents for the work, and every decision is written down in documents that stay in the repository.
Two lanes:
ask— you want an answer. The PM answers. Nothing changes.team— you want a change. The PM runs the crew: one task per change, one round of QA, one round of each review, then a commit. Pushing and publishing still need your own yes, every time.
Install
dsh plugin --profile tui add dsh-crew # or --profile web
Restart dsh. Pick the Crew preset for a session.
Quick start
- Install the plugin (above).
- Restart dsh.
- Start a session on the Crew preset. Your session becomes the PM.
- Ask a question, or ask for a change.
Configuration
Everything is optional. Settings live in two places:
- The
dsh-crew-coreanddsh-crew-git-guardrows in your profile'scordis.patch.yml: roles folder, live-agent limit, review rounds, job folder, and the git guard. - The
dsh-crew-rolesrow in~/.dsh/.agent-presets/crew/agent.cordis.yml: per-role tools and models.
License
MIT
Links
More in this category
Q00/ouroboros#integrations/dsh-plugin★ 6173
Config-only bundle that mounts Ouroboros through the DSH MCP client, exposing 36 interview, Seed, execution, evaluation, and evolution workflow tools in DSH.
loopx-project/loopx#dsh-loopx-plugin★ 6136
LoopX, a provider-neutral, local-first state kernel and control plane for long-horizon agents: keeps Goal, Todo, gate, evidence, quota, recovery, and handoff state above DeepSeek Harness, while the plugin bootstraps the CLI and skills, admits bounded same-session continuation, and adds a loopback GoalBar for the exact bound loop.
chuspeeism/dashi-taskboard#deepseek-harness★ 3276
Embeds the active installed Codex Taskboard runtime in the DeepSeek Harness sidebar, using its launcher runtime descriptor instead of a fixed port.
NanmiCoder/dsh-agent-teams★ 1893
AgentTeams multi-agent teams.
EthanYoQ/AI-Novel-Writer#dsh-ai-novel-writer★ 1263
Installs a dedicated AI novel-writing preset and workbench: revisioned local project assets, a compact side drawer, and native approval-gated single-file changes.
tong-io/tongflow#dsh-tongflow★ 1035
TongFlow film-crew studio for image, voice, music and video production: the agent writes per-asset TongFlow workflow files (.tongflow.json) that run through TongFlow plugins, with an embedded workflow canvas, a shot/character/take project layout and a manga-drama template; sessions starting with @tongflow open the Studio view.
Community comments
Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.