Ito

💬 نظرات

• کاربر ProductHunt 1Hey Product Hunt. I'm Evan, cofounder of Ito. Coding agents produce more code than you can review. Existing code review tools only stare at the code, so you still have to review tons of code or build complex internal systems to verify it. Ito is a runtime code review tool. On every pull request: Creates test plan from code, PR description, ticket, your input Builds your app in a single-use isolated container with the ability to use credentials, seed data to reach the state that matters, and use external services just as an engineer would on their local machine. Mocks data/code when it doesn’t have access. Drives the app with a swarm of agents (click, navigate, API call, db verification) Catches runtime issues: concurrency, failure handling, data migration, authentication, etc. Posts results on PR with evidence: video, logs, screenshots We built Ito with a team of 8 MIT engineers, and spent many cycles to arbitrarily build any application.  Ito gets better the more you use it: Responds to feedback Faster runtimes every run as Ito learns how to navigate your application and builds tools to manipulate your environment Reviews focused on the areas you care about (sees what gets fixed vs ignored) Test instruction per org, per repo, or per author First 100 reviews free, no card. $40/mo after that. Free forever for open source (already supporting >100k stars): app.ito.ai?ph You can also try out open source PRs without signing up here: https://www.ito.ai/review?ph
• کاربر ProductHunt 2Really interesting approach! How does Ito handle cases where the app environment can't be fully reproduced because of private services, credentials, or production-only dependencies?
• کاربر ProductHunt 3The combination of isolated environments + agent-driven testing + runtime evidence is what really stands out here. Curious to see how well Ito handles complex state, flaky external services, and large monorepos.
• کاربر ProductHunt 4Running the app before reading the diff is the actual difference here, and it creates a question I have not seen a runtime reviewer answer well. What does Ito post on the PR when the container itself never came up? Build failed, seed data unavailable, external service refused the credential. If that lands as "no runtime issues found", then a broken environment and a clean PR are the same result, and it fails silently in the direction that looks fine. So: what does a run that could not run report as?