Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-better-sidebar | dsh-session-archive | dsh-git-graph |
|---|---|---|---|
| Platforms | DeepSeek Harness | DeepSeek Harness | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | Apache-2.0 | Apache-2.0 |
| Stars | 4478 | 9384 | 9384 |
| Last activity | September 23, 2026 | September 26, 2026 | September 25, 2026 |
| Install complexity | سهل / Easy | Easy | سهل / Easy |
| Category | Code Review, Git, Workflow, UI | Memory, Security, Workflow | Git, Workflow, UI |
| Best use | Best for a developer using DeepSeek Harness who wants session files, changes, and parallel jobs visible beside the conversation. It adds session-specific context and separates Side Chat questions from the main flow. It is not a standalone full IDE and requires a compatible DSH release. | 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. |