Ito (runtime code review) (@QAwithIto) header
Ito (runtime code review) (@QAwithIto) profile picture

Only code review that runs your code. Remove manual testing bottlenecks in 5 minutes. Ito finds regressions and logic errors before you merge.

San Francisco
Joined May 2025
Photo by Ito (runtime code review) (@QAwithIto)Photo by Ito (runtime code review) (@QAwithIto)Photo by Ito (runtime code review) (@QAwithIto)Photo by Ito (runtime code review) (@QAwithIto)Photo by Ito (runtime code review) (@QAwithIto)Photo by Ito (runtime code review) (@QAwithIto)Photo by Ito (runtime code review) (@QAwithIto)Photo by Ito (runtime code review) (@QAwithIto)Photo by Ito (runtime code review) (@QAwithIto)Photo by Ito (runtime code review) (@QAwithIto)
81% of Ito's findings aren't found in the diff. Catch runtime bugs that only show up when actually running and testing the application.
1
2
5
58,657
Thanks for the continued support on our @ProductHunt launch 😺🚀📈 Excited to help devs ship faster with code review that actually runs your code
3
1
30
4,425
BUG OF THE WEEK: @freshdesk integration technically correct & passed static checks (@ChatGPT codex), but at runtime the requests get rate-limited leading to sync issues and incorrect state. Quick fix once the issue was identified: "The shared importer now snapshots the persisted cursor and stats, performs cursor/stat writes under the DataImport row lock, preserves a newer cursor, and rebuilds counters from persisted items and mappings when it detects concurrent state. The regression uses two separately loaded DataImport records and verifies that a delayed cursor-1 / imported-count-1 worker cannot overwrite the committed cursor-2 / imported-count-2 / processed-count-2 state. Focused Freshdesk and Intercom validation passed 98 examples with 0 failures, and RuboCop plus git diff --check are clean."
20
4,209
just moved into our humble new office
i'm late to share this. we moved into a new @dodopayments office in indiranagar. 3x bigger than our last one. a year ago we went from a 9-seater to a 30-seater thinking we'd have room for a while. we didn't. the team outgrew it fast enough that we had to split up. my team stayed in the original office, @goelrishabh's team moved into the antler office. took two months to find the right space. now everyone's back under one roof. it's not really about the office. it's about what the office means. more merchants, a stronger product, and a team that keeps outgrowing every space we put it in. and it won't just be ours. we're opening it up to bangalore builders. build irl ep 1 already happened here.
Readers added context they thought people might want to know
As Ayush later admitted, the office photos were AI-generated or altered, yet the post wasn't labeled using X's available AI disclosure option. While not illegal, this misrepresents the company's reality and warrants a Community Note. Source --x.com/ayushagarwal/s…
1
1
1
19
4,138
Ito (runtime code review) retweeted
Ito is a runtime analysis code review agent. Builds your app from a PR branch and runs real tests against it. For Doltgres: real SQL, real Postgres wire protocol. Over 6 wks: 43 PRs, 2:1 signal-to-noise. Caught long-standing bugs they didn't know existed. dolthub.com/blog/2026-07-20-…
1
3
24
4,534
Ito (runtime code review) retweeted
Running parallel coding agents? Worktrees isolate your files, but your DB, ports, and services still collide. moo gives every agent its own Linux VM, versioned with your repo. Fork a 20 GB machine in under a second. moove faster: github.com/heyito/moo
2
5
32
5,685
Happy Fourth of July! Celebrate with independence from bugs
15
5,228
Launched a new review page to quickly test Ito on your repo can TRY ITO FREE and see open source examples that are similar to your app Time to finally catch the runtime issues your ai code is generating faster and without looking at every line ito.ai/review
1
1
1
27
5,214
agents have a sense of humor. I didn't have access to the YT video for homepage when testing, so decided to #rickroll the team. full test plan below
3
1
1
19
4,900
also caught a bug 🥅🐞
2
7
606
Static analysis has a ceiling. If your whole QA stack relies on it, your users are eating the bugs you should be catching. Agents can stare at code all day long, but they won't find all the issues because they are probabilistic unit tests. Doesn't matter how many tokens you burn here $1-25 / PR get's similar results. You need to run your application to get runtime evidence that code behaves as your organization expects 1 /
2
3
1
22
84,056
AI review tools made the reading step faster and more consistent. Organizations adopting AI code tools still introduce 300% more bugs per PR. To move at the speed you want, it is impossible to read every line.
1
5
738
Fable is by far the best model to blow through your monthly token budget in just a few hours.
Introducing Claude Fable 5: a Mythos-class model that we’ve made safe for general use. Its capabilities exceed those of any model we’ve ever made generally available.
2
16
5,252
Ito (runtime code review) retweeted
Replying to @QAwithIto
@QAwithIto is in good company on @OpenRouter 's Leaderboard the first day we started tracking. Everyone coding 10x wants to verify they're building the right thing. We validate the behavior of your code. That simple.
3
5
2
46
12,828
Huge thanks to @_ai_collective for hosting the SF demo night. We are so excited to have won the overall best AI award!
Nights like SF Demo Night are a powerful reminder of why the tech scene here is so incredibly special!
1
3
1
40
7,947