Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-git-graph | Hurl | act |
|---|---|---|---|
| Platforms | DeepSeek Harness | Universal | GitHub |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | Apache-2.0 | Apache-2.0 | MIT |
| Stars | 9384 | 19271 | 72437 |
| Last activity | September 25, 2026 | October 17, 2026 | — |
| Install complexity | سهل / Easy | Easy; API and CLI knowledge required | — |
| Category | Git, Workflow, UI | Testing, DevOps | Testing, Git, 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 small team that wants repeatable API checks with explicit conditions stored beside the code. It links request data and identifies failing assertions without repeating manual inspection. It does not replace browser tests or test-environment setup; curl may be enough for a one-off request. | Best for a developer or small team that repeatedly edits GitHub Actions workflows and wants to test a job before pushing. It provides a local run log, while a final GitHub check remains necessary. It is not suitable when exact hosted-runner parity is required. |