Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | marimo | zoxide | act |
|---|---|---|---|
| Platforms | Universal | Universal | GitHub |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | Apache-2.0 | MIT | MIT |
| Stars | 23382 | 40380 | 72501 |
| Last activity | October 29, 2026 | October 24, 2026 | — |
| Install complexity | EASY | — | — |
| Category | Workflow, Data | Workflow | Testing, Git, DevOps |
| Best use | 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. | Best for a developer or small team that repeatedly edits GitHub Actions workflows and wants to test a job before pushing. It provides a local run log, while a final GitHub check remains necessary. It is not suitable when exact hosted-runner parity is required. |