Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-agent-teams | dsh-session-archive | Hurl |
|---|---|---|---|
| Platforms | DeepSeek Harness | DeepSeek Harness | Universal |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | Apache-2.0 | Apache-2.0 |
| Stars | 2386 | 9384 | 19271 |
| Last activity | — | September 26, 2026 | October 17, 2026 |
| Install complexity | يتطلب إصدار DSH متوافقًا وإعادة تشغيل | Easy | Easy; API and CLI knowledge required |
| Category | Multi-Agent, Workflow | Memory, Security, Workflow | Testing, DevOps |
| 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 or small team that wants repeatable API checks with explicit conditions stored beside the code. It links request data and identifies failing assertions without repeating manual inspection. It does not replace browser tests or test-environment setup; curl may be enough for a one-off request. |