Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | Backlog.md | act | dsh-session-archive |
|---|---|---|---|
| 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 | 7131 | 72437 | 9384 |
| Last activity | — | — | September 26, 2026 |
| Install complexity | Easy — npm, Bun, Homebrew, or Nix | — | Easy |
| Category | Multi-Agent, Git, Workflow | Testing, Git, DevOps | Memory, Security, Workflow |
| 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. | 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. |