Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-agent-teams | DuckDB | dsh-session-archive |
|---|---|---|---|
| Platforms | DeepSeek Harness | Universal | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | MIT | Apache-2.0 |
| Stars | 2386 | 42451 | 9384 |
| Last activity | — | September 28, 2026 | September 26, 2026 |
| Install complexity | يتطلب إصدار DSH متوافقًا وإعادة تشغيل | سهل — حزمة Python أو ملف CLI تنفيذي واحد | Easy |
| Category | Multi-Agent, Workflow | Database | 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 an analyst, developer, or small team that needs to inspect and join large data files and rerun analysis locally. It adds reviewable SQL without database-server setup. It is not a multi-user transactional database for many small concurrent writes from 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. |