Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-session-archive | dsh-git-graph | uv |
|---|---|---|---|
| Platforms | DeepSeek Harness | DeepSeek Harness | Universal |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | Apache-2.0 | Apache-2.0 | MIT OR Apache-2.0 |
| Stars | 9384 | 9384 | 91072 |
| Last activity | September 26, 2026 | September 25, 2026 | October 20, 2026 |
| Install complexity | Easy | سهل / Easy | Easy on supported systems; Homebrew must already be installed for this command. Windows and standalone installation options are explained in the guide. |
| Category | Memory, Security, Workflow | Git, Workflow, UI | Workflow, DevOps |
| 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. | For a Python developer or small team that wants a shared setup rather than relying on manually installed packages. Commit the dependency definition and lockfile, then sync the environment and run commands with uv. It does not isolate the operating system or untrusted code, or replace application compatibility tests. |