Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-git-graph | act | dsh-session-archive |
|---|---|---|---|
| Platforms | DeepSeek Harness | GitHub | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | Apache-2.0 | MIT | Apache-2.0 |
| Stars | 9384 | 72437 | 9384 |
| Last activity | September 25, 2026 | — | September 26, 2026 |
| Install complexity | سهل / Easy | — | Easy |
| Category | Git, Workflow, UI | Testing, Git, DevOps | Memory, Security, Workflow |
| Best use | 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 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. | 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. |