Skip to lesson
Exit
Browser verification with page evidence1 / 2

2 min lesson

Verify one browser flow

Run one exact browser path, inspect its page and runtime evidence, then capture the final state.

Step 1 of 2

Choose one changed web flow and write down its URL, test data, steps and expected result. Ask Agent to use Browser on that path. Watch the page change, read the relevant console messages and inspect the request that carries the changed data. If the evidence exposes a bug, fix only that cause. Repeat the same path, then keep the final screenshot and runtime evidence with the handoff.

Verify the cart in the Browser tab

0:22 · narrated
Read this demo as text
  1. Ask the agent to open the local cart in Browser and read the total. Typecheck will not show a wrong price on the page.
  2. Browser shows the Acme cart. Changes stays next to it — evidence beside the run, not buried in the editor alone.
Open the Agents Browser tab on the live cart — UI proof lives beside the run, not only in the diff.

Practice next: Now try it: ask the agent to open a local page in Browser, switch to the Browser tab, and confirm what the page shows before you merge.

Simulated Cursor 3.12 (macOS, light) — beta educational reconstruction, not the real product.