Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | Miller | dsh-task-board | dsh-git-graph |
|---|---|---|---|
| Platforms | Universal, MCP, Claude Code, Codex, Cursor | DeepSeek Harness | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | BSD-2-Clause | Apache-2.0 | Apache-2.0 |
| Stars | 10049 | 9384 | 9384 |
| Last activity | October 21, 2026 | — | September 25, 2026 |
| Install complexity | EASY | Intermediate | سهل / Easy |
| Category | Workflow, Data | Multi-Agent, Workflow | Git, Workflow, UI |
| Best use | 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. | Best for a developer or small team using DSH for recurring or connected work and wanting task state and execution evidence in one record. It pins the project, agent preset, and permission, then runs manually or through Host cron with a human gate for elevated access. It is not a fit for a frequently sleeping machine or unreviewed sensitive automation. | 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. |