Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for any developer or team that wants a terminal-native coding agent you own — model choice is one config change, permission policy is declarative, session history stays on disk, MCP and skills work from the same CLI, and the headless `zero exec` mode is shaped for real CI use (text/JSON/stream-JSON I/O, isolated worktrees, spec-first runs, meaningful exit codes). The 25+ provider surface is
Who should use it
Who should skip it
Consider Gitlawb/zero lower priority if you already have a working solution in this category.
About this signal
Gitlawb/zero is tracked by RepoRadar as a go 1.25+ terminal coding agent ( in the Coding Agents section. It was first seen on 2026-07-04 and last updated on 2026-07-04. The current verdict is 'try now' with a Gold tier and easy setup difficulty. Gitlawb/zero leads on workflow potential (9.6) and practical usefulness (9.0); its lowest signal is maturity (6.4), so factor that in before investing setup time. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned Gitlawb/zero a composite score of 8.1 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'low' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
Risk label is still being reviewed from the captured evidence. Treat the item as unknown-risk until you review the linked source, permissions, setup path, and data access.