Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-agent-teams | Backlog.md | dsh-git-graph |
|---|---|---|---|
| Platforms | DeepSeek Harness | Universal, Codex, Claude Code, Cursor | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | MIT | Apache-2.0 |
| Stars | 2386 | 7131 | 9384 |
| Last activity | — | — | September 25, 2026 |
| Install complexity | يتطلب إصدار DSH متوافقًا وإعادة تشغيل | Easy — npm, Bun, Homebrew, or Nix | سهل / Easy |
| Category | Multi-Agent, Workflow | Multi-Agent, Git, Workflow | Git, Workflow, UI |
| 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 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. | Best for a developer running several DSH sessions against one repository who wants visible branch context, history, and worktree creation in the UI. It adds session isolation and readable branch-switch guards. It may be excessive for one small change on one branch or for environments that prohibit outbound telemetry. |