Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-git-graph | Superpowers | ntfy |
|---|---|---|---|
| Platforms | DeepSeek Harness | Claude Code, Codex, Cursor, OpenCode | Universal |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | Apache-2.0 | MIT | Apache-2.0 / GPL-2.0 |
| Stars | 9384 | 304170 | 35017 |
| Last activity | September 25, 2026 | — | September 29, 2026 |
| Install complexity | سهل / Easy | — | سهل للتجربة، متوسط للاستضافة الآمنة / Easy to try, moderate to self-host securely |
| Category | Git, Workflow, UI | Code Review, Multi-Agent, Testing, Workflow | Workflow, DevOps |
| Best use | 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 a developer or project owner working on a substantial feature or a difficult bug. It helps clarify requirements, approve a plan, and inspect tests and file changes. Its value is a visible path from decision to verification. A small text edit may not need the full workflow. | 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. |