Automatic smoke test every night, every release, or on-demand.

Three ways, and all three work together. First, the actual code changes and relevant PR description: this is zero-shot and works with no setup. Second, instructions your team sets at the repo, user, or organization level to prioritize what matters most, like security, mobile usability, or accessibility. Third, what Ito learns over time from the bugs your team fixes or closes as won't fix and the feedback you give on test plans. The result is a plan targeted at the real risk surface of that change, personalized to your team and sharper with every run.

A full test plan tagged by category and visible in your dashboard and in GitHub. After execution, you get a complete report: tests run, issues found with severity classification, reproduction steps, video evidence, screenshots, and the specific lines of code responsible for each failure.

When Ito finds a problem, it is classified independently by severity based on business impact (Critical, High, Medium, Low) and by whether it is attributable to the current release or pre-existing.

Yes. Add plain-English instructions at the org or repo level to tell Ito which flows to prioritize, deprioritize, or skip on specific test types. You can ask Ito to run additional tests after a run completes.

Ito is configurable so you can trigger smoke tests as you see fit. Ito tests every PR by default. Layer in smoke tests on timed cadence, based off a GitHub workflow, or on-demand triggers like Slack.