Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | Backlog.md | dsh-git-graph | Task |
|---|---|---|---|
| Platforms | Universal, Codex, Claude Code, Cursor | DeepSeek Harness | Universal, GitHub |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | Apache-2.0 | MIT |
| Stars | 7130 | 9384 | 16276 |
| Last activity | — | September 25, 2026 | — |
| Install complexity | Easy — npm, Bun, Homebrew, or Nix | سهل / Easy | سهل / Easy |
| Category | Multi-Agent, Git, Workflow | Git, Workflow, UI | Workflow, DevOps |
| Best use | 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. | Best for a developer or small team whose project commands span languages, folders, and tools. It provides documented entry points that people and agents can use and review in Git. Existing scripts may be enough for a simple project; Task does not install project tools or sandbox their commands. |