Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | D2 | goose | Hurl |
|---|---|---|---|
| Platforms | Universal | Universal, MCP | Universal |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MPL-2.0 | Apache-2.0 | Apache-2.0 |
| Stars | 25761 | 55946 | 19288 |
| Last activity | October 11, 2026 | October 23, 2026 | October 17, 2026 |
| Install complexity | Easy with a supported package manager; Homebrew must already be installed for this command. Official binaries, Windows, Linux, and source options are documented. | MEDIUM | Easy; API and CLI knowledge required |
| Category | Workflow, UI | Code Review, Multi-Agent, Workflow | Testing, DevOps |
| Best use | For developers and small teams that want architecture and data-flow diagrams close to the repository and reviewable as text. Use it when relationships matter more than pixel-perfect placement; not for free-form marketing design or exact manual positioning. | 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. | 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. |