Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-agent-teams | Miller | dsh-task-board |
|---|---|---|---|
| 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 | 2386 | 10049 | 9384 |
| Last activity | — | October 21, 2026 | — |
| Install complexity | يتطلب إصدار DSH متوافقًا وإعادة تشغيل | EASY | Intermediate |
| Category | Multi-Agent, Workflow | Workflow, Data | Multi-Agent, Workflow |
| 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. | 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 using DSH for recurring or connected work and wanting task state and execution evidence in one record. It pins the project, agent preset, and permission, then runs manually or through Host cron with a human gate for elevated access. It is not a fit for a frequently sleeping machine or unreviewed sensitive automation. |