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