Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | Dagu | zoxide | act |
|---|---|---|---|
| Platforms | Universal, MCP | Universal | GitHub |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | GPL-3.0 | MIT | MIT |
| Stars | 4491 | 40353 | 72477 |
| Last activity | October 28, 2026 | October 24, 2026 | — |
| Install complexity | سهل للبداية؛ يحتاج ضبط أمان قبل المشاركة / Easy to start; security configuration required before sharing | — | — |
| Category | Workflow, DevOps, Monitoring | Workflow | Testing, Git, DevOps |
| Best use | Best for a developer or small team with connected scripts that need schedules, history, and a clear failure point. It adds dependencies, retries, and an operations UI without an external database in single-server mode. A simple independent command may not need it, and some team controls such as additional users, SSO, RBAC, and audit logging currently require a paid license. | 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. |