Greptile’s Post

Today, we announce Greptile's $4.1M seed round, led by Initialized Capital with participation from Y Combinator, Richard Aberman, and JJ Fliegelman. We are building the AI expert that *truly* understands your codebase. It can answer hard questions about your codebase, review your pull requests with full context of your repos, and much, much more. We even offer Greptile as an API so you can build custom internal tools with it. Greptile started as a hackathon project last July, and now serves developers at over 500 companies. We are growing very fast. If you're an engineer passionate about building the future of AI-enable software development, join us!

Greptile's new code review bot summarizes and reviews changes with full context of your codebase. It catches bugs, code repetition, and anti-patterns better than humans. No more waiting for review, no more interrupting your flow for reviews. It takes <15 minutes to set up on a Zoom call (cal.com/greptile/15min to book), it's free for the first month, and when it reviews your first PR, we send you this cool SHIP FASTER crew neck. Join the 500+ teams that use Greptile to ship faster.

🦎Greptile can now review your pull requests! The hardest part about reviewing PRs is having full context of the codebase, which is exactly what Greptile is great at! Greptile's PR review bot can comment on things like: ✨ potential bugs introduced by the changes ✨ potential security issues introduced by the changes ✨ duplicate code which may exist elsewhere in the codebase ✨ potentially missed edge cases ...and more! Learn more here 👉 https://lnkd.in/eiwnEiHx

My absolute *favorite* internal tool that we have built on the Greptile API is our Linear bot. When there is a new Linear issue, it adds a comment with -> ✨ Files/directories in the repo that are relevant to the issue. ✨ References to code in your repo that is similar to what I am about to write. ✨Instructions on how to do the issue, with notes on security, compliance, and code health considerations. When I see a new issue, within *30 seconds* I am primed what I parts of the codebase I need to look at, if there is already code in the codebase that is similar to what I am about to write, and if there is anything non-obvious that i should keep in mind while doing this task. Use our API or Zapier to build your own Greptile linear bot today!

🦎Greptile is now live on Zapier 🎉! If you're building internal AI dev tools for your team, you can now easily use Greptile+Zapier to add full codebase context! Some examples 👇 ✨ Integrate Linear or Asana to add descriptions to every ticket with codebase context. ✨ Integrate Slack to let Greptile instantly answer any codebase related questions, saving time for everyone. ✨ Integrate Sentry (sentry.io) to get codebase context-aware reports on every alert. ✨ Integrate GitHub to generate PR comments to make review 10X faster! ...and much, much more! Interested in checking it out? Go to Zapier's website and search for "Greptile" 💪

I asked 100 developers at top companies why they aren't shipping faster. My team and I at Greptile are obsessed with helping software teams ship faster. Two months ago, we set out to ask 100 developers at companies ranging from Amazon to Palantir Technologies to Zillow, why they aren't able to ship faster. After doing the interviews, I was surprised by two things: 1. Almost no-one had to think about it. People shot back with immediate answers, as though I had just asked about pain that was always on their minds, but never surfaced by another person. 2. There were a surprisingly high number of people for whom the reason had to do with build, compile, and deploy times. Devs really hate waiting for things. Check out our full report featuring quotes from dozens of top tier engineers and bar charts showing the top causes for slow shipping speed at software companies. (Link in comments)

This is the 🦎 Greptile (YC W24) feature that BLOWS potential customers away in demos. 👇 Let's say you're facing a bug in a particular repo. 1️⃣ Simply log in to Greptile with GitHub and select the repo. 2️⃣ Paste in the error message you are seeing. 3️⃣ Greptile finds where the error is coming from, explains the cause, and gives you fixed code 🤯 Here's a video of me using it a few nights ago to solve an annoying bug 👇 Greptile fixed it first try! Your smartest coworker now lives on your browser ✨

🎉 Last night, we announced our new name -> 🦎 Greptile (YC W24). Soohoon C., Vaishant Kameswaran and I created Onboard AI to help developers onboard onto new codebases. Over the last 7 months, as thousands of developers used it, we realized it was much, much more than an onboarding tool. Turns out that all developers, not just new hires, are slowed down by large codebases. What we have built is the world's first AI-native codebase search and comprehension tool. We needed a new name to reflect this expanded scope. "Greptile" is a play on `grep`, the linux command used for running regular expression searches across multiple files and directories. Greptile is certainly a polarizing name. You either love it or hate it. One thing's for certain - you won't forget it.