A check is a run with the recording turned off. Screen Browser signs in, walks the main guide step by step, and reports for every step how the target was found (from the guide, remembered from an earlier run, or learned on the spot) with a small screenshot of the page afterwards. No narration, no video, no credits.
A check performs the steps. If the guide creates a record in your app, the check creates one too. Every button that starts a check says so.
Where
- The 🔍 Check button on every guide on the project page.
- Check in the guide editor.
- Check first on the last step of the new-project wizard.
Checks are not on the MCP server on purpose: an agent's failed run is free anyway and teaches the recorder the same things.
Limits
Starter has 20 checks a day, Pro and above 100. A check that stopped early still counts, because it still used a recorder. A check that failed on our side (a crash, a page that never loaded) does not count.
Reading the report
The run page lists every step: the line as written, how it resolved, and the screenshot. A step marked learned means the page called the thing something else and the recorder found it; the pick is remembered on the guide version and shown in the editor, where you can pin a different target. A step marked skipped was an optional step whose element was not there.