Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-session-archive | dsh-git-graph | 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 | Apache-2.0 | MIT |
| Stars | 9384 | 9384 | 304147 |
| Last activity | September 26, 2026 | September 25, 2026 | — |
| Install complexity | Easy | سهل / Easy | — |
| Category | Memory, Security, Workflow | Git, Workflow, UI | 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 running several DSH sessions against one repository who wants visible branch context, history, and worktree creation in the UI. It adds session isolation and readable branch-switch guards. It may be excessive for one small change on one branch or for environments that prohibit outbound telemetry. | 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. |