Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | Backlog.md | dsh-session-archive | dsh-git-graph |
|---|---|---|---|
| Platforms | Universal, Codex, Claude Code, Cursor | DeepSeek Harness | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | Apache-2.0 | Apache-2.0 |
| Stars | 7130 | 9384 | 9384 |
| Last activity | — | September 26, 2026 | September 25, 2026 |
| Install complexity | Easy — npm, Bun, Homebrew, or Nix | Easy | سهل / Easy |
| Category | Multi-Agent, Git, Workflow | Memory, Security, Workflow | 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. | Use it when DSH sessions pile up and you need to identify old work, archive it first, then safely remove what is no longer needed while protecting running sessions. It fits recurring cleanup and finished projects; do not enable automatic deletion before previewing the policy and checking backups. | 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. |