Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-git-graph | Miller | Backlog.md |
|---|---|---|---|
| Platforms | DeepSeek Harness | Universal, MCP, Claude Code, Codex, Cursor | Universal, Codex, Claude Code, Cursor |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | Apache-2.0 | BSD-2-Clause | MIT |
| Stars | 9384 | 10049 | 7131 |
| Last activity | September 25, 2026 | October 21, 2026 | — |
| Install complexity | سهل / Easy | EASY | Easy — npm, Bun, Homebrew, or Nix |
| Category | Git, Workflow, UI | Workflow, Data | Multi-Agent, Git, Workflow |
| Best use | 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. | Ideal for developers, data analysts, and operators who need to clean a CSV export, inspect JSON Lines, or summarize a large file from the terminal without starting a Python project. Use it for quick, repeatable file processing; concurrent transactions and advanced visual analysis still call for a database or complementary analytics tool. | 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. |