Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | DuckDB | dsh-session-archive | dsh-git-graph |
|---|---|---|---|
| Platforms | Universal | DeepSeek Harness | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | Apache-2.0 | Apache-2.0 |
| Stars | 42451 | 9384 | 9384 |
| Last activity | September 28, 2026 | September 26, 2026 | September 25, 2026 |
| Install complexity | سهل — حزمة Python أو ملف CLI تنفيذي واحد | Easy | سهل / Easy |
| Category | Database | Memory, Security, Workflow | Git, Workflow, UI |
| Best use | Best for an analyst, developer, or small team that needs to inspect and join large data files and rerun analysis locally. It adds reviewable SQL without database-server setup. It is not a multi-user transactional database for many small concurrent writes from separate processes. | 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. |