Greptile

What do you like best about the product?

The GitHub integration is seamless, once the repo is connected, Greptile automatically triggers a review on every pull request without any manual steps. The setup process is straightforward, and the dashboard gives a clean overview of PR activity, review scores, and bugs caught over time. The keyboard shortcuts in the Pull Requests tab are a thoughtful touch for power users. I also appreciate that it works silently in the background, fitting naturally into an existing dev workflow without disrupting it.

What do you dislike about the product?

All three of my test PRs, including one with a Python file containing a deliberate division-by-zero bug and a JavaScript file with undefined functions and missing null checks, were scored 4/5 with a "Low" severity rating. While the reviews completed quickly, the consistent scoring across very different code quality levels raises questions about how granular the risk assessment actually is. There's no severity breakdown per issue, and the dashboard doesn't surface what specific bugs were caught without clicking into each PR individually. A summary view of flagged issues across all PRs would make the analytics far more actionable. The persistent payment banner during the free trial also feels premature.

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

Greptile addresses one of the most time-consuming bottlenecks in software development, manual code review. In teams where senior developers are stretched thin, PRs often sit unreviewed for hours or days, slowing down delivery. Greptile acts as a first-pass AI reviewer that instantly flags potential bugs, risky patterns, and code quality issues the moment a PR is raised, without waiting for a human reviewer to be available. For my use case, it integrated directly with GitHub in minutes and began reviewing PRs automatically, no configuration per PR needed. The scoring system (out of 5) gives a quick at-a-glance signal of PR health, and the bugs-caught metric on the analytics dashboard helps teams track code quality trends over time. For L&D and non-engineering teams exploring AI-assisted development workflows, it lowers the barrier to maintaining code quality standards without needing deep technical oversight on every commit.

What do you like best about the product?

How much easier it makes working with a large unfamiliar codebase. Instead of spending ages digging through files trying to understand how everything connects, I can ask questions in a more natural way and get useful context quickly.

What do you dislike about the product?

That the quality of the responses can sometimes depend on how well I phrase my question.

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

Mainly solves the problem of trying to understand unfamiliar or complex code without having to manually work through every file. When I need to understand how something works, where an issue might be coming from, or what could be affected by a change, it gives me a much quicker starting point

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.