Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-agent-teams | dsh-task-board | Backlog.md |
|---|---|---|---|
| Platforms | DeepSeek Harness | DeepSeek Harness | Universal, Codex, Claude Code, Cursor |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | Apache-2.0 | MIT |
| Stars | 2386 | 9384 | 7131 |
| Last activity | — | — | — |
| Install complexity | يتطلب إصدار DSH متوافقًا وإعادة تشغيل | Intermediate | Easy — npm, Bun, Homebrew, or Nix |
| Category | Multi-Agent, Workflow | Multi-Agent, Workflow | Multi-Agent, Git, Workflow |
| Best use | For development work that can be divided into dependent tasks and reviewed as a plan before agents start. Monitor outputs and model costs; team state is not coordinated across separate processes. | Best for a developer or small team using DSH for recurring or connected work and wanting task state and execution evidence in one record. It pins the project, agent preset, and permission, then runs manually or through Host cron with a human gate for elevated access. It is not a fit for a frequently sleeping machine or unreviewed sensitive automation. | Best for an individual developer or small team using coding agents and wanting to review the specification and plan before code. It keeps tasks, acceptance criteria, and decisions inside the project and exposes them through CLI, a local browser, or MCP. It is not a replacement for a centralized enterprise SaaS board with organization-wide permissions and reporting. |