Greptile

What do you like best about the product?

Reviewing massive pull requests used to be the biggest bottleneck in our development cycle. Greptile completely changes this by indexing our entire codebase into a comprehensive graph. Unlike basic AI tools that only look at the immediate diff, Greptile evaluates how changes impact cross-file dependencies, shared logic, and related modules. For example, it successfully catches API default mismatches between frontend and backend architectures before the code ever reaches a staging environment. The T-REX (Test, Run, EXecute) feature is incredibly powerful, as it actually writes and executes tests in an isolated sandbox to validate PRs dynamically. Furthermore, if it flags an issue, the native integration lets us send the context directly to local IDE agents like Cursor or Claude Code to instantly apply the fix.

What do you dislike about the product?

Because the core system relies on LLMs, it suffers from inherent stochasticity; a single pass might occasionally miss highly specific edge cases that a rigid, deterministic static analyzer would easily catch. Additionally, out of the box, the AI can sometimes be overly noisy on massive PRs. It requires active team participation—specifically using the thumbs-up or thumbs-down reactions on its comments—for the reinforcement learning engine to adapt to our specific coding standards. Until the system learns those preferences or until you properly configure the .greptile.json file, developers might spend time dismissing false positives.

What problems is the product solving and how is that benefiting you?

It acts as a continuous, automated validation layer that catches complex logic errors and security vulnerabilities early in the pipeline. By surfacing structural and cross-layer issues immediately on the pull request, it drastically cuts down on back-and-forth communication. This has tangibly reduced our average PR merge times and freed up senior engineers to focus strictly on architectural decisions and product design, rather than hunting for broken contracts across different files.

What do you like best about the product?

We have been using greptile for a long time and we like multiple things. 1. The comments on PR's are quite detailed and helpful with a button to fix directly with Claude, which gives a very good user experience. 2. Has very good integration with GITHUB. 3. Even on big PR's it gives the comments after analyzing in a very short time.

What do you dislike about the product?

1. Pricing could be better than their competitor. 2. Misses the overall picture of the PR - which could be improved though.

What problems is the product solving and how is that benefiting you?

Greptile helps us speed up the development cycle, especially by doing a first-pass review of code changes. It’s useful because once it identifies the basic issues, a senior developer doesn’t have to spend a lot of time carefully checking for those simple problems, and can instead focus on more complex logic.

What do you like best about the product?

I like that Greptile makes code reviews easier and helps catch issues that I might miss. It is easy to use and saves time when reviewing code.

What do you dislike about the product?

Sometimes the suggestions are not fully accurate, so I still like to check them myself. Other than that, I don't have any major complaints.

What problems is the product solving and how is that benefiting you?

It helps me save time during code reviews by finding issues that I might miss myself. It also makes it easier to review changes and catch problems early.

What do you like best about the product?

I like the Greptile reviews code with the context of the wider codebase instead of looking only at the changed lines. It catches issues that can be easy to miss during a manual review.

What do you dislike about the product?

Some reviews can take a little longer, especially when the changes are more complex, and I still need to verify some of the suggestions before acting on them.

What problems is the product solving and how is that benefiting you?

It reduces the amount of manual code-review work by checking pull requests for bugs and issues across the codebase. This makes it easier to catch problems before they reach production.

What do you like best about the product?

True Repository Context: It doesn’t just read the pull request diff; it understands our entire codebase structure, microservices, and dependencies. Extremely Low Noise: It flags critical architectural and security bugs without spamming developers with annoying, nitpicky style comments. Massive Time Savings: It provides accurate, inline PR reviews within minutes, which has significantly reduced our development cycle times.

What do you dislike about the product?

It lacks a free tier and adds a $1 per-review overage tax, along with a tight platform restriction to only GitHub and GitLab. Additionally, despite recent accuracy updates, teams can still occasionally run into high comment volume or non-actionable “noise” on pull requests, which means you may need to invest some initial time and effort to fine-tune the system’s severity thresholds for your specific codebase.

What problems is the product solving and how is that benefiting you?

Greptile solves the bottleneck of slow, inconsistent code reviews and the struggle of navigating massive, complex repositories. By instantly analyzing pull requests with full codebase context, it frees up senior developers from tedious review cycles and catches critical architectural bugs before they hit production. This has drastically cut our development cycle times, elevated code quality, and allowed our team to ship features faster without compromising security.