Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | Superpowers | dsh-session-archive | dsh-task-board |
|---|---|---|---|
| Platforms | Claude Code, Codex, Cursor, OpenCode | DeepSeek Harness | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | Apache-2.0 | Apache-2.0 |
| Stars | 304147 | 9384 | 9384 |
| Last activity | — | September 26, 2026 | — |
| Install complexity | — | Easy | Intermediate |
| Category | Code Review, Multi-Agent, Testing, Workflow | Memory, Security, Workflow | Multi-Agent, Workflow |
| Best use | Best for a developer or project owner working on a substantial feature or a difficult bug. It helps clarify requirements, approve a plan, and inspect tests and file changes. Its value is a visible path from decision to verification. A small text edit may not need the full workflow. | 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 or small team using DSH for recurring or connected work and wanting task state and execution evidence in one record. It pins the project, agent preset, and permission, then runs manually or through Host cron with a human gate for elevated access. It is not a fit for a frequently sleeping machine or unreviewed sensitive automation. |