Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | Dagu | Lazygit | Backlog.md |
|---|---|---|---|
| Platforms | Universal, MCP | Universal | Universal, Codex, Claude Code, Cursor |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | GPL-3.0 | MIT | MIT |
| Stars | 4491 | 83506 | 7196 |
| Last activity | October 28, 2026 | October 15, 2026 | — |
| Install complexity | سهل للبداية؛ يحتاج ضبط أمان قبل المشاركة / Easy to start; security configuration required before sharing | سهل للتثبيت؛ يحتاج معرفة Git / Easy to install; Git knowledge required | Easy — npm, Bun, Homebrew, or Nix |
| Category | Workflow, DevOps, Monitoring | Code Review, Git | Multi-Agent, Git, Workflow |
| 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. | Best for a solo developer or small team that works from the terminal and wants focused, reviewable commits. It helps select changes and open another branch in a separate working folder. It does not replace tests or Git knowledge; your editor interface may already be enough. | Best for an individual developer or small team using coding agents and wanting to review the specification and plan before code. It keeps tasks, acceptance criteria, and decisions inside the project and exposes them through CLI, a local browser, or MCP. It is not a replacement for a centralized enterprise SaaS board with organization-wide permissions and reporting. |