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