Daksh Gupta is cofounder and CEO of Greptile, which develops AI tools for reviewing software changes. His work focuses on how a review system can understand the surrounding codebase and help teams validate an increasing volume of code written with agents.[1][2][3]
Start with AI-Generated Code Is Already Competing With Human Code — Daksh Gupta, Greptile →
Career
Gupta met his cofounders at Georgia Tech. Their CREATE-X project began as an AI shopping assistant called Tabnam, then shifted toward helping developers understand software. He describes wanting a tool that could learn a codebase and help with debugging and quality assurance. Greptile emerged from that work and continued through Y Combinator’s winter 2024 program.[2][4]
Contributions
Greptile’s current product reviews pull requests using context from the repository and connected development tools. Its website describes investigating the affected code and testing proposed changes rather than treating a diff as an isolated text passage. Gupta leads the company with his cofounders and team; the review system is their product.[1][4][6]
Ideas
Measure generated code using several signals
In his AI Engineer talk, Gupta compares agent-associated and human-written pull requests using revert rates, issue severity and review rounds. He explains how his analysis identifies generated changes through metadata and other signals. These observations concern the reviewed repositories and detection method, rather than proving that all generated code has the same quality as all human code.[5]
Ask what a change does to the application’s contract
The talk connects review to three questions: whether a change breaks expected behavior, makes a future break more likely or fulfills its author’s intent. Gupta uses blast-radius analysis and sandboxed browser testing to illustrate the approach. This makes code validation a question about application behavior and surrounding dependencies, extending beyond whether a patch compiles.[5]
Tools, writing & talks
Writing, research & talks
Start here
A talk comparing pull-request quality signals and explaining a behavior-focused approach to validation.
Start with the four quality measures and the explanation of how generated changes were identified. Familiarity with pull requests helps; compare the analysis method with your own repositories before generalizing its conclusions.
Speaker[5]Original source- Founder Spotlight: Greptile’s Daksh Guptainitialized.com
An early interview about moving from a college project to a codebase-understanding product.
Interview participant[2]