Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-git-graph | goose | dsh-chrome |
|---|---|---|---|
| Platforms | DeepSeek Harness | Universal, MCP | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | Apache-2.0 | Apache-2.0 | MIT |
| Stars | 9384 | 55590 | 9 |
| Last activity | September 25, 2026 | October 23, 2026 | — |
| Install complexity | سهل / Easy | MEDIUM | متوسط / Moderate |
| Category | Git, Workflow, UI | Code Review, Multi-Agent, Workflow | Browser Automation, Security |
| 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 an individual developer or small team that wants an AI agent to complete an inspectable task in a working copy: understand files, make a bounded change, and run a test. Start with manual approval and scope the folder and tools. Do not give it broad access to production or sensitive data. | 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. |