Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | Bruno | marimo | zoxide |
|---|---|---|---|
| Platforms | Universal | Universal | Universal |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | Apache-2.0 | MIT |
| Stars | 47971 | 23389 | 40394 |
| Last activity | October 30, 2026 | October 29, 2026 | October 24, 2026 |
| Install complexity | EASY | EASY | — |
| Category | Testing, Git | Workflow, Data | Workflow |
| Best use | Ideal for a solo developer or small team that wants API collections and tests beside the code with Git review. Use it for repeatable REST, GraphQL, gRPC, and WebSocket checks—not live cloud collaboration or load testing. | Ideal for a data analyst, Python developer, or small team that wants reproducible experiments, clear Git review, and an interactive report or internal tool from the same source. It is not a replacement for governed BI or a production service requiring enterprise scaling and permissions. | For developers switching among many directories in an interactive terminal. It learns from visited paths and helps you return; use explicit paths for scripts and deployments that require a fixed destination. |