Thanks @greptile team for having us! It was an amazing opportunity for heavy users (like us 😁) to directly discuss the technical details and best practices with the team!
The difference between AI slop code and not that much AI slope code.
So grateful to have @greptile
If you work on open-source project make sure to apply: greptile.com/open-source
My agent engineering hacks (inspired by @mvanhorn's must read)
1. eslint, ci-cd, & code-review (shoutout @greptile) are your guardians. guardrail the crap out of your repo. eslint gives you deterministic tests.
2. keep your codebase well documented. Use top level AGENTS(dot)md
introducing the greptile CLI.
a full greptile review for your local changes, right in your terminal.
1. npm i -g greptile
2. checkout your branch
3. greptile review 🦎
introducing the greptile CLI.
a full greptile review for your local changes, right in your terminal.
1. npm i -g greptile
2. checkout your branch
3. greptile review 🦎
We review code for 22,000 teams, and we don't use one AI model to do it. Each job goes to the model that fits it best.
We put @nvidia Nemotron 3 Ultra to the test on two of the most demanding: ~4.5x cheaper reply classification and 62% cheaper indexing in beta. Read how, then
introducing repo clusters
you can now group related repos into a cluster, like frontend, backend and docs. when greptile reviews a PR on one of those repos, it will have complete context of the others.
greptile will also intelligently suggest clusters