Run a bounded browser review
Keep a browser review small enough to inspect, with explicit actions and evidence.
Updated 2026-09-15
A bounded review can make a smaller model useful: give it one page, a short sequence, and a precise report. Choose from the models and browser tools available to your configured provider. Cost depends on that configuration and usage; this recipe makes no price comparison.
Worked example: check a settings dialog
Illustrative.
01 · Goal
Check scrolling and keyboard behavior in one dialog.
02 · Setup
Provide a running preview with non-sensitive data and an agent configuration that can operate its browser. Define the URL and which dialog to open.
03 · Prompt
Review only the specified settings dialog. Do not edit files or submit changes.
At desktop and narrow mobile widths, open it, tab through controls, and scroll
to both boundaries. Check whether wheel input moves the obscured page.
Close it with Escape and report where focus returns. Return the viewport sizes,
steps, observations, and screenshots that contain no private data.
Do not delegate. Stop after this sequence.04 · Evidence produced
Observations tied to each action and viewport, plus safe screenshots where useful.
05 · User review
Reproduce reported failures and inspect the evidence. A successful sequence establishes only the interactions exercised, not overall accessibility or the absence of other bugs.
See Review and source changes for evaluating the report.