Short answer: Amar Goel says Bito also runs in Cursor, Windsurf, Claude Code, VS Code and JetBrains and flags cross-service issues. With teams on mixed tools and PRs so big reviews take days, he says a formal gate check is needed.
Watch this answer from Episode 23 (starts at 8:05) · Episode 23 notes and transcript
From Episode 23: OpenAI Code Red? The New AI Reviewer Changing Everything, starting at 8:05.
Jordan Metzner [8:05]: Awesome. So, just so I, like, understand correctly, I you know, I'm a big user. Obviously, like and some of these other tools you mentioned. Obviously, they're great for reviewing the code you just wrote that minute, because it is in some sense or the code it just wrote that minute. But to your point, for, like, a large mono repo or a large microservice based repo, it's really hard to get any of these tools to be able to index that amount of quantity. None of them have the ability to do that. And so what happens for us as developer is you're able to analyze what you wrote or what the AI just vibe coded but not how well that fits within your entire code base both like stylistically security, etcetera. Right? And so essentially, I guess, these integrations, I guess, of writing these vibe codes with this classic code base end up failing and hence where your tool comes in most value. Is that like the best way to put it?
Amar Goel [8:52]: Yeah. Yeah. I think the way I would think about it is, like yeah. So we actually have, like, you can run our review in Cursor and Windsurf and, Claude Code and stuff as well. So, we Studio Code, JetBrains. So, like, lots of teams use our agent in their IDE as well to review their code because, what we're able to do is, again, with all the different tools and the agentic approach, like, we're able to just go much deeper. We break up each diff into a different view or understanding, like, maybe you do have like, for example, a simple thing would be, like, you're just reviewing some code and you say, like, oh, well, you didn't have error handling. Well, maybe that team doesn't really care about error handling or the error handling is being handled more upstream. Right? So those kinds of things. Or again, because you have that deeper understanding of the whole code base, you're able to say, hey, you've changed these this service here, but now, that's gonna result in a problem in this upstream service that that calls it, you know. So you're able to, like, point out those issues, in a much deeper way. And so I think, yeah, I think if you have, like, a simple kind of, code base or you're just doing a Vibe Coded project, yeah, I don't think Bito is, like, probably necessary for you. But I think if you live in, like, an enterprise environment, that really makes a difference. Some something that's, a real quality gate.
Amar Goel [10:10]: The other thing I would kinda just mention is we're seeing a real proliferation of these tools. Right? So, as you go into larger companies, like, some people are in Cursor, some people are in Claude Code, and so, a lot of times people like, oh, well, front end team is using this other thing or, we're using, some back end developers using JetBrains. So then you're kind of in this mode of, like, well, is everyone actually reviewing their code locally? We really need a formal kinda gate check as this code is going to production. And I think the other thing we're seeing is that the amount of code that everyone's producing is going up dramatically. And so if you don't really have, like, a formal kinda gate check, who knows what's kinda getting into production? I mean, we've seen teams tell us things like PRs are getting so big that reviewing code is taking days now. And also when a bug gets into production, the developer a lot of times didn't even write the code. So nobody really knows what's going on anymore.
Amar Goel [11:12]: You know? It's everyone's like, I gotta go check and figure this out. It's so different than two, three years ago where it's like what somebody's like, I wrote that code. I deeply understand how it works, and I can start thinking about how this bug might be happening. Now people are like, well, I scanned the bug. Maybe I ran some unit tests, but, like, I need to go, like, learn this code now to understand why there's this production issue.
