Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-task-board | dsh-git-graph | DuckDB |
|---|---|---|---|
| Platforms | DeepSeek Harness | DeepSeek Harness | Universal |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | Apache-2.0 | Apache-2.0 | MIT |
| Stars | 9384 | 9384 | 42451 |
| Last activity | — | September 25, 2026 | September 28, 2026 |
| Install complexity | Intermediate | سهل / Easy | سهل — حزمة Python أو ملف CLI تنفيذي واحد |
| Category | Multi-Agent, Workflow | Git, Workflow, UI | Database |
| Best use | Best for a developer or small team using DSH for recurring or connected work and wanting task state and execution evidence in one record. It pins the project, agent preset, and permission, then runs manually or through Host cron with a human gate for elevated access. It is not a fit for a frequently sleeping machine or unreviewed sensitive automation. | 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. | 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. |