As many developers use agentic tools to create more code faster than ever before, the code has gotten more complex and they’re taking longer to find and fix software flaws. Helping to address that pressure is a key concern at Google. We know that software development velocity is increasing, as much as 2x for some teams , and the average developer fix time for software flaws expanded from approximately 59 days a decade ago to more than 170 days in 2025, according to the Mandiant M-Trends 2026 Report .

To help you secure more code, more quickly, we’ve built CodeMender, our autonomous code-security agent that can find and fix software flaws at machine speed. We also know that developer tools only succeed if they fit into existing routines. That’s why CodeMender, part of our AI Threat Defense platform , brings automated code fixes directly into the developer workflow. Today, we’re sharing this reference architecture that wires automated CodeMender remediation straight into Git pull requests via Google Cloud Run. Everything happens in the timeline.

The scan posts one comment, a table of findings, each finding with an ID, and the two things you can type next. Figure 1: A pull request triggers the scan on Cloud Run. Findings, exploit traces, and proposed patches all come back to the same timeline. Reply /verify 612424da and the exploit attempt comes back in the thread, folded into a collapsible View Exploit Steps & Response Trace block so it doesn't bury the conversation. Reply /fix 612424da and the patch arrives the same way, behind Preview Proposed Code Diff , with a draft pull request already open /approve there. Both commands take all in place of an ID.

Figure 2: The initial scan comment provides a table of findings and the actionable slash commands, keeping the developer entirely within the pull request timeline. Nothing asks the developer to leave the pull request or learn a console. CodeMender cm find runs return a confidence score on the vulnerability finding during the code analysis. If the confidence score is below 100%, you can use cm verify to have CodeMender build and simulate an exploit in a sandbox to determine if the vulnerability is actually exploitable. The simulation results can change the severity.