Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | goose | ntfy | dsh-git-graph |
|---|---|---|---|
| Platforms | Universal, MCP | Universal | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | Apache-2.0 | Apache-2.0 / GPL-2.0 | Apache-2.0 |
| Stars | 55588 | 35016 | 9384 |
| Last activity | October 23, 2026 | September 29, 2026 | September 25, 2026 |
| Install complexity | MEDIUM | سهل للتجربة، متوسط للاستضافة الآمنة / Easy to try, moderate to self-host securely | سهل / Easy |
| Category | Code Review, Multi-Agent, Workflow | Workflow, DevOps | Git, Workflow, UI |
| Best use | Best for an individual developer or small team that wants an AI agent to complete an inspectable task in a working copy: understand files, make a bounded change, and run a test. Start with manual approval and scope the folder and tools. Do not give it broad access to production or sensitive data. | Best for an individual developer or small team that wants backup, deployment, and scheduled-job alerts without building a notification app. It starts with one HTTP request and can be self-hosted with users and ACLs. It is not a complete incident-management or log-retention system. | 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. |