Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-session-archive | dsh-chrome | Backlog.md |
|---|---|---|---|
| Platforms | DeepSeek Harness | DeepSeek Harness | Universal, Codex, Claude Code, Cursor |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | Apache-2.0 | MIT | MIT |
| Stars | 9384 | 9 | 7131 |
| Last activity | September 26, 2026 | — | — |
| Install complexity | Easy | متوسط / Moderate | Easy — npm, Bun, Homebrew, or Nix |
| Category | Memory, Security, Workflow | Browser Automation, Security | Multi-Agent, Git, Workflow |
| Best use | 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 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. | 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. |