Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-agent-teams | MarkItDown | 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 | 2386 | 191797 | 9384 |
| Last activity | — | — | September 25, 2026 |
| Install complexity | يتطلب إصدار DSH متوافقًا وإعادة تشغيل | سهل / Easy | سهل / Easy |
| Category | Multi-Agent, Workflow | Workflow, Research | Git, Workflow, UI |
| Best use | For development work that can be divided into dependent tasks and reviewed as a plan before agents start. Monitor outputs and model costs; team state is not coordinated across separate processes. | Best for a developer or analyst extracting text from several document formats before search or supplying selected passages to an AI agent. It provides a repeatable CLI command and Python library, while requiring review against the original. It is not intended for layout-perfect document publishing. | 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. |