Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-agent-teams | dsh-session-archive | dsh-chrome |
|---|---|---|---|
| Platforms | DeepSeek Harness | DeepSeek Harness | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | Apache-2.0 | MIT |
| Stars | 2386 | 9384 | 9 |
| Last activity | — | September 26, 2026 | — |
| Install complexity | يتطلب إصدار DSH متوافقًا وإعادة تشغيل | Easy | متوسط / Moderate |
| Category | Multi-Agent, Workflow | Memory, Security, 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. | Use it when DSH sessions pile up and you need to identify old work, archive it first, then safely remove what is no longer needed while protecting running sessions. It fits recurring cleanup and finished projects; do not enable automatic deletion before previewing the policy and checking backups. | 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. |