How Code Mower works
Code Mower starts local, adds peer reviewer lanes carefully, measures their signal, and only shares metadata with CodeMower.com when a team opts in.
1. Install the local OSS tool
Install Code Mower from the public repository at github.com/codemower-ai/code-mower, then run code-mower init --easy in the repository you want to pilot.
2. Run doctor before enabling lanes
code-mower doctor --preflight checks Python, GitHub auth, private-repo Actions cost traps, provider CLI setup, token posture, and optional cloud readiness. Warnings are setup guidance before any reviewer lane surprises the team. It is equivalent to the versioned doctor --v05 preset used in scripts.
3. Start manual and local
Codex and Claude are the first structured local audit lanes. Hosted reviewers and extra provider integrations start informational until calibration data proves they are useful on the actual codebase.
4. Measure reviewer value
Build a calibration corpus from known-clean and known-blocked pull requests. Code Mower turns that into a value report with useful-rate, false positives, cost, latency, and lane recommendations.
5. Optionally upload metadata
Teams that want private dashboards can create a team token on CodeMower.com and upload sanitized metadata. Cross-team cohort benchmarks are roadmap work, not live product value yet. Local reports remain useful without a hosted account.
Start with the early adopter setup or review the privacy and data boundary.