Browser control on a running app1 / 2

2 min lesson

Debug one login-gated settings flow

Reproduce one login-gated settings bug, inspect its runtime evidence and stop before the destructive submit.

Find the running development server and open http://localhost:3000/settings. Check the visible account and tenant because Browser keeps workspace storage between sessions. Use the seeded qa@acme.test account. Approve the navigation, click and type actions separately, then reproduce the disabled confirmation button without submitting deletion. Read the related console lines and the name-check request in the Agent panel. Fix only the trailing-space cause. Repeat the same URL, account and steps. Confirm the 200 response, enabled button and absence of the related console error, then capture the final screenshot and stop before deletion.

Drive the page, then report what changed

0:35 · narrated

Read this demo as text

Ask the agent to actually click Apply on the live cart — not just tell you the coupon exists. A number typed in chat proves nothing; a number read off the page does.
Switch to the Browser tab and watch the agent drive the page itself — click Apply, and the cart total recalculates right there.
Fifty dollars becomes forty-five. The agent reports the number it just read off the running page — browser-verified, not guessed from the code.

Watch Browser apply a coupon on the live cart and read the new total from the page.

Practice next: Now run the login-gated settings flow with a seeded test account and stop before the destructive submit.

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

Learn more

Full explanation

Browser navigation, workspace session, console, network, screenshot

Debug one login-gated settings flow

Browser navigation, workspace session, console, network, screenshot

SayThe confirmation button on /settings stays disabled after login. The browser workspace may already hold an old cookie, so check the account before touching the form.

DoFind the running development server and open http://localhost:3000/settings. Confirm the visible account and tenant. If needed, sign in manually as the seeded qa@acme.test user.

SeeThe browser is on /settings as the intended test user. No production account or real customer data is in the flow.

DoApprove the navigation, click and type actions one at a time. Open the Delete account dialog and type Acme Inc, but do not approve the final deletion.

SeeThe confirmation button stays disabled, which reproduces the bug without changing the account.

DoRead the relevant console lines and the name-check request in the Agent panel. Check its payload and response instead of scanning every browser log.

SeeThe request sends Acme Inc with a trailing space and returns 409. The related console line reports the same mismatch.

DoTrim the value in the confirmation handler and leave the rest of the flow alone. Repeat the same URL, account and steps.

SeeThe name-check returns 200, the confirmation button enables and no related console error remains.

DoCapture settings-delete-confirmed.png with the account, dialog and enabled button visible. Stop before the destructive submit and attach the console and request evidence to the handoff.

SeeA reviewer can reproduce the safe test and inspect the page, response and final state.

Learn more

Optional practice

Test yourself on Debug one login-gated settings flow

QWhich result proves the login-gated Browser flow is ready for review?