Google describes Sashiko's real-world Linux kernel agent code-review results

Google published a November 19 engineering account of Sashiko, its open-source Gemini-powered Linux kernel code-review system. It reports roughly 1,200 reviews daily across more than 100 mailing lists, with over 70 lists opting into review emails. The architecture separates specialist passes for different bug classes from independent verification of disputed findings and even questionable dismissals.
Google reports Sashiko citations in more than 2,000 mainline commits and 500 kernel CVEs this year. It also observed lower subsequent fix rates after rollout, while explicitly cautioning that many other factors could explain the change.
A deployed AI review system offers rare operational measurements and a reproducible architecture for validating code changes.
Read full briefing Collapse briefing
Detailed briefing
Specialists and verification
Sashiko gathers code around a proposed diff, including relevant callers, structures and subsystem notes, then launches up to seven focused review sessions. They separately investigate intent, control flow, resource lifetimes, locking, security and hardware interactions. Each records not only suspected defects but also concerns it investigated and dismissed. A lead verifier audits both lists and sends ambiguous claims to independent per-bug verification agents, requiring code evidence rather than speculation.
Production data and developer feedback
Google says the system completes around 1,200 reviews a day, with more than 1,500 kernel developers having replied to its reports. It cites more than 2,000 mainline commits and over 500 CVEs that mention Sashiko. The reported 60-day follow-up fix rate fell from a historical 3.4% to 2.2% for a later release, but this before/after comparison is observational. Changes in release mix, review culture and reporting practices may contribute.
Reproduction and engineering implications
The project is open source, with review traces and prompts made public. Its most transferable design principle is to require independent evidence for both positive bug findings and dismissals, rather than treating model confidence as proof. Running similarly deep reviews can be costly: Google funds the public service, and the system averages extensive repository tool use. It complements rather than replaces experienced maintainers.
Limitations & caveats
Reported outcome correlations are not causal proof that the agent reduced bugs.
