Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-agent-teams | dsh-task-board | 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 | 2386 | 9384 | 9384 |
| Last activity | — | — | September 25, 2026 |
| Install complexity | يتطلب إصدار DSH متوافقًا وإعادة تشغيل | Intermediate | سهل / Easy |
| Category | Multi-Agent, Workflow | Multi-Agent, Workflow | Git, Workflow, UI |
| Best use | For development work that can be divided into dependent tasks and reviewed as a plan before agents start. Monitor outputs and model costs; team state is not coordinated across separate processes. | 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. |