Greptile takes bug detection beyond code review with GPT-6 Astra
Oct 26, 2026, 3:00 PM · OpenAI

Greptile is betting that AI-written code now ships faster than humans can test it, so it is pointing computer-use agents at apps to break them before users do.
Why it matters
Greptile builds AI agents that review and test code changes with the full context of a codebase. In a customer story published by OpenAI, the company says it now uses GPT-6 Astra's computer-use abilities to actually run applications during review: spin up a development server for a pull request, resize the browser to an iPhone-sized screen, click through like a user and visually spot problems, such as a button that disappears on mobile.
The argument is about pace. Co-founder and CEO Daksh Gupta says a human QA firm testing every change is impractically slow given how quickly teams now ship code with AI models. If that is right, automated behavioral testing stops being a nice-to-have and becomes the safety net for AI-accelerated development.
From the desk
We think this is one of the more sensible uses of agentic AI we've seen pitched. Reading code catches some bugs; running the app catches others. Having an agent behave like an impatient user on a small phone screen is exactly the kind of tedious, high-value checking that tends to get skipped under deadline pressure. Greptile's other metric is also the right one: it tracks how often AI-generated code gets reverted, and says giving Codex its documentation through an MCP server means fewer reverts.
But keep the source in view. This is an OpenAI customer story about an OpenAI customer, featuring OpenAI's models, Daybreak security product and Ultrafast. It offers no revert rates, bug counts or before-and-after numbers, only the claim that thousands of customers have connected Codex to Greptile's knowledge base. We take the direction seriously and the magnitude as unproven.
There is a deeper loop worth naming. AI writes code faster, so AI has to review it, so AI has to test it, and the reason given for skipping human QA is that humans are now too slow. Each step is reasonable. Put together, it can mean critical software where no person fully understood the change before it shipped. Gupta's stated long-term goal is making critical enterprise software as easy to ship as a side project. We'd argue critical systems should stay a little harder to change than side projects, and the friction is partly the point.
The security framing deserves attention too. Gupta says stronger models make attacks easier, putting even small companies at risk that previously would not have been targets. That is a sober point, and it is the best case for giving startups better automated defenses. It also means the same capability is spreading on both sides.
Our read: automated, behavior-level testing is a genuine improvement and should become standard. Just don't let it become the reason humans stop looking at what ships to banks, hospitals and infrastructure.
Context
Greptile's Knowledge Base indexes a company's codebase and documents how it works for both people and agents. The company says it uses Codex heavily for its own engineering and sees model speed, not intelligence, as its main bottleneck.
Who feels it
- Developers
- Agents that run apps and test real user flows can catch visual and behavioral bugs that code review misses.
- QA teams
- Routine manual testing is being reframed as too slow, pushing human testers toward oversight and edge cases.
- Startups
- Cheaper automated testing and security tooling could narrow the gap with well-resourced companies as attacks get easier.
- Critical-system operators
- Faster shipping raises the stakes of any gap in verification for software that people depend on.
What to watch
- Published revert or defect data from Greptile customers
- Wider adoption of computer-use agents in pull-request testing
- Daybreak results in real customer security programs
- Whether regulated industries accept automated QA in place of human sign-off
Companies: OpenAI