Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-chrome | Docusaurus | dsh-git-graph |
|---|---|---|---|
| Platforms | DeepSeek Harness | Universal | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | MIT | Apache-2.0 |
| Stars | 9 | 66577 | 9384 |
| Last activity | — | October 16, 2026 | September 25, 2026 |
| Install complexity | متوسط / Moderate | Moderate: Node.js >=20, project files, build and hosting workflow | سهل / Easy |
| Category | Browser Automation, Security | Workflow, DevOps | 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. | Best for a developer or small team maintaining a product or library guide and comfortable with files and Git. It organizes scattered instructions into pages with clear locale and version choices. It does not write or translate your content, and may be excessive for a single page or a team needing direct collaborative editing. | 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. |