Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | DuckDB | dsh-task-board | dsh-session-archive |
|---|---|---|---|
| Platforms | Universal | DeepSeek Harness | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | Apache-2.0 | Apache-2.0 |
| Stars | 42451 | 9384 | 9384 |
| Last activity | September 28, 2026 | — | September 26, 2026 |
| Install complexity | سهل — حزمة Python أو ملف CLI تنفيذي واحد | Intermediate | Easy |
| Category | Database | Multi-Agent, Workflow | Memory, Security, Workflow |
| Best use | 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. | Best for a developer or small team using DSH for recurring or connected work and wanting task state and execution evidence in one record. It pins the project, agent preset, and permission, then runs manually or through Host cron with a human gate for elevated access. It is not a fit for a frequently sleeping machine or unreviewed sensitive automation. | 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. |