Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-git-graph | Backlog.md | dsh-chrome |
|---|---|---|---|
| Platforms | DeepSeek Harness | Universal, Codex, Claude Code, Cursor | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | Apache-2.0 | MIT | MIT |
| Stars | 9384 | 7131 | 9 |
| Last activity | September 25, 2026 | — | — |
| Install complexity | سهل / Easy | Easy — npm, Bun, Homebrew, or Nix | متوسط / Moderate |
| Category | Git, Workflow, UI | Multi-Agent, Git, Workflow | Browser Automation, Security |
| 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. | 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 debugging a local or test web UI who wants a DSH agent to see the page and network evidence in the same session. It reduces manual copying and supports interactive inspection after an explicit request. Avoid it for sensitive production accounts or if broad browser permissions are unacceptable. |