Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-agent-teams | goose | dsh-chrome |
|---|---|---|---|
| Platforms | DeepSeek Harness | Universal, MCP | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | Apache-2.0 | MIT |
| Stars | 2386 | 55590 | 9 |
| Last activity | — | October 23, 2026 | — |
| Install complexity | يتطلب إصدار DSH متوافقًا وإعادة تشغيل | MEDIUM | متوسط / Moderate |
| Category | Multi-Agent, Workflow | Code Review, Multi-Agent, Workflow | Browser Automation, Security |
| 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 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. |