Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | Superpowers | dsh-session-archive | act |
|---|---|---|---|
| Platforms | Claude Code, Codex, Cursor, OpenCode | DeepSeek Harness | GitHub |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | Apache-2.0 | MIT |
| Stars | 304170 | 9384 | 72437 |
| Last activity | — | September 26, 2026 | — |
| Install complexity | — | Easy | — |
| Category | Code Review, Multi-Agent, Testing, Workflow | Memory, Security, Workflow | Testing, Git, DevOps |
| 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 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. |