2 min lesson
Drive the UI with the integrated browser
Use "Cursor's integrated browser has Playwright under the hood, so the agent can drive real browser actions" to describe the practical rule.
Step 1 of 2
Drive the UI with the integrated browserfor the bugs that only show in the app
Some repros are a sequence of clicks, not a script. Cursor's integrated browserCursor's built-in browser, driven by Playwright under the hood, so the agent can navigate, click, screenshot and capture each action's metadata while you watch. Press Enter for the full definition. has Playwright under the hood, so the agent can drive real browser actions - click a button, navigate a page, take a screenshot - and capture the metadata of each step. While it runs, a banner on the right says the agent is using the browser and a step log builds on the left. Ask it to write each accessed element out to a text file and you have a recorded, replayable trace of the exact path that triggers the bug.
Because the actions are Playwright underneath, the flow you prototype to reproduce a UI bug is one step from being an integration test. Drive the broken path once, capture the steps, then keep them as a regression guard so the bug can't come back silently.
our integrated browserCursor's built-in browser, driven by Playwright under the hood, so the agent can navigate, click, screenshot and capture each action's metadata while you watch. Press Enter for the full definition. actually has Playwright under the hood.
If you genuinely can't reproduce, that's not a dead end - it's a deliverable. Document exactly what you tried, what you ruled out and the conditions you couldn't recreate. "I ran it 30 times across two OSes and three models without a repro; it only appears on the user's corp network" tells engineering precisely where to look next. Negative results are signal when they're specific.
Don't declare a nondeterministic bug "fixed" off one good run or "present" off one bad one. With stochastic output you need a before-and-after rate. Showing a regression from 30% failure to 2% is convincing; showing one passing run is luck.