Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-git-graph | Miller | Docusaurus |
|---|---|---|---|
| Platforms | DeepSeek Harness | Universal, MCP, Claude Code, Codex, Cursor | Universal |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | Apache-2.0 | BSD-2-Clause | MIT |
| Stars | 9384 | 10049 | 66577 |
| Last activity | September 25, 2026 | October 21, 2026 | October 16, 2026 |
| Install complexity | سهل / Easy | EASY | Moderate: Node.js >=20, project files, build and hosting workflow |
| Category | Git, Workflow, UI | Workflow, Data | Workflow, DevOps |
| 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. | 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 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. |