Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-agent-teams | Gatus | dsh-git-graph |
|---|---|---|---|
| Platforms | DeepSeek Harness | Universal | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | Apache-2.0 | Apache-2.0 |
| Stars | 2386 | 12381 | 9384 |
| Last activity | — | September 24, 2026 | September 25, 2026 |
| Install complexity | يتطلب إصدار DSH متوافقًا وإعادة تشغيل | سهل إلى متوسط / Easy to moderate | سهل / Easy |
| Category | Multi-Agent, Workflow | Security, DevOps | 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 an individual developer or small team that wants self-hosted website, API, DNS, and certificate checks with a status page and threshold-based alerts. It combines active checks and simple history in one service. It does not replace resource monitoring, logs, or distributed tracing. | 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. |