Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-agent-teams | act | dsh-session-archive |
|---|---|---|---|
| Platforms | DeepSeek Harness | GitHub | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | MIT | Apache-2.0 |
| Stars | 2386 | 72437 | 9384 |
| Last activity | — | — | September 26, 2026 |
| Install complexity | يتطلب إصدار DSH متوافقًا وإعادة تشغيل | — | Easy |
| Category | Multi-Agent, Workflow | Testing, Git, DevOps | Memory, Security, 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. | Best for a developer or small team that repeatedly edits GitHub Actions workflows and wants to test a job before pushing. It provides a local run log, while a final GitHub check remains necessary. It is not suitable when exact hosted-runner parity is required. | 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. |