Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-chrome | Miller | dsh-git-graph |
|---|---|---|---|
| Platforms | DeepSeek Harness | Universal, MCP, Claude Code, Codex, Cursor | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | BSD-2-Clause | Apache-2.0 |
| Stars | 9 | 10049 | 9384 |
| Last activity | — | October 21, 2026 | September 25, 2026 |
| Install complexity | متوسط / Moderate | EASY | سهل / Easy |
| Category | Browser Automation, Security | Workflow, Data | Git, Workflow, UI |
| Best use | Best for a developer debugging a local or test web UI who wants a DSH agent to see the page and network evidence in the same session. It reduces manual copying and supports interactive inspection after an explicit request. Avoid it for sensitive production accounts or if broad browser permissions are unacceptable. | 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 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. |