Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-session-archive | Miller | dsh-git-graph |
|---|---|---|---|
| Platforms | DeepSeek Harness | Universal, MCP, Claude Code, Codex, Cursor | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | Apache-2.0 | BSD-2-Clause | Apache-2.0 |
| Stars | 9384 | 10049 | 9384 |
| Last activity | September 26, 2026 | October 21, 2026 | September 25, 2026 |
| Install complexity | Easy | EASY | سهل / Easy |
| Category | Memory, Security, Workflow | Workflow, Data | 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. | Ideal for developers, data analysts, and operators who need to clean a CSV export, inspect JSON Lines, or summarize a large file from the terminal without starting a Python project. Use it for quick, repeatable file processing; concurrent transactions and advanced visual analysis still call for a database or complementary analytics tool. | 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. |