Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | Backlog.md | act | dsh-git-graph |
|---|---|---|---|
| Platforms | Universal, Codex, Claude Code, Cursor | GitHub | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | MIT | Apache-2.0 |
| Stars | 7130 | 72437 | 9384 |
| Last activity | — | — | September 25, 2026 |
| Install complexity | Easy — npm, Bun, Homebrew, or Nix | — | سهل / Easy |
| Category | Multi-Agent, Git, Workflow | Testing, Git, DevOps | Git, Workflow, UI |
| 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 or small team that repeatedly edits GitHub Actions workflows and wants to test a job before pushing. It provides a local run log, while a final GitHub check remains necessary. It is not suitable when exact hosted-runner parity is required. | 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. |