Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | Task | dsh-session-archive | Superpowers |
|---|---|---|---|
| Platforms | Universal, GitHub | DeepSeek Harness | Claude Code, Codex, Cursor, OpenCode |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | Apache-2.0 | MIT |
| Stars | 16277 | 9384 | 304170 |
| Last activity | — | September 26, 2026 | — |
| Install complexity | سهل / Easy | Easy | — |
| Category | Workflow, DevOps | Memory, Security, Workflow | Code Review, Multi-Agent, Testing, Workflow |
| Best use | Best for a developer or small team whose project commands span languages, folders, and tools. It provides documented entry points that people and agents can use and review in Git. Existing scripts may be enough for a simple project; Task does not install project tools or sandbox their commands. | 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 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. |