Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | Hurl | goose | dsh-session-archive |
|---|---|---|---|
| Platforms | Universal | Universal, MCP | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | Apache-2.0 | Apache-2.0 | Apache-2.0 |
| Stars | 19271 | 55592 | 9384 |
| Last activity | October 17, 2026 | October 23, 2026 | September 26, 2026 |
| Install complexity | Easy; API and CLI knowledge required | MEDIUM | Easy |
| Category | Testing, DevOps | Code Review, Multi-Agent, Workflow | Memory, Security, Workflow |
| Best use | 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. | Best for an individual developer or small team that wants an AI agent to complete an inspectable task in a working copy: understand files, make a bounded change, and run a test. Start with manual approval and scope the folder and tools. Do not give it broad access to production or sensitive data. | 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. |