Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-git-graph | act | Miller |
|---|---|---|---|
| Platforms | DeepSeek Harness | GitHub | Universal, MCP, Claude Code, Codex, Cursor |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | Apache-2.0 | MIT | BSD-2-Clause |
| Stars | 9384 | 72437 | 10049 |
| Last activity | September 25, 2026 | — | October 21, 2026 |
| Install complexity | سهل / Easy | — | EASY |
| Category | Git, Workflow, UI | Testing, Git, DevOps | Workflow, Data |
| 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 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. | Ideal for developers, data analysts, and operators who need to clean a CSV export, inspect JSON Lines, or summarize a large file from the terminal without starting a Python project. Use it for quick, repeatable file processing; concurrent transactions and advanced visual analysis still call for a database or complementary analytics tool. |