When should you use it?
- You build web front ends locally
- You often switch to the browser to check a change
- You want faster write-test-fix loops
Not for: Full regression suites across many flows; Cross-browser compatibility testing
What do you need, and what do you get?
You need
- Anthropic's terminal agent or desktop app
- The Chrome add-on
- A local dev server
You get
- Changes verified in the running app
- Browser error messages spotted and resolved
- Notes on what was clicked and seen
How does it work, step by step?
- Install and connectAdd the extension, then start Claude Code with its Chrome flag or the in-session command.
- Run your dev serverHave the app up on localhost so the agent can open it.
- Ask for change plus checkRequest the feature and a click-through of the affected screens.
- Have it check browser errorsThe agent picks up errors and fixes them before reporting done.
- Watch the billBrowser steps eat context quickly; the authors recommend a flat subscription for heavy use.
The prompt
Our own prompt, inspired by Test-Lab.ai and written to work in Claude Code and Claude. Values in lime are placeholders.
Implement [change] in this app. Then open http://localhost:[port] in my Chrome, go through [screens or flow], and check the console for errors. Fix anything you find and repeat the click-through. Report what you tested, what you saw, and anything you could not verify. Do not visit sites other than localhost.
Inspired by Test-Lab.ai: Claude Code + Chrome Extension: The Best Local Dev Testing Setup Right Now | Test-Lab.ai. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- The authors document stability problems with alternative browser tools over many months.
- It checks the flow you asked about, not the dozens of other flows a change can break.
Our take
This is a practical write-up with a clear conflict-of-interest note, which we appreciate from a testing vendor. The setup is worth trying for front-end work because the agent seeing its own UI output closes the loop that pure code review misses. Keep the agent in a browser profile without banking, payroll or production admin sessions, since it shares whatever you are logged into. Treat its click-through as a smoke test, not a release gate: it catches obvious breakage and console errors, while accessibility, edge cases and real user flows still need proper tests. Compare cost with Playwright-style tools for repetitive suites; browser-driving agents burn tokens quickly on long sessions, which is why the authors prefer a subscription. Ask for a short report of what it clicked and what failed, so you can spot flaky steps. Close the shared browser profile when the coding session ends. Prefer a dedicated test user account inside the app under test.
Where the time goes back: Removing the manual switch to the browser after every edit shortens each iteration noticeably.
FAQ
Why not Playwright MCP?
Is the author neutral?
Source and credit
Inspired by Test-Lab.ai. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Claude Code + Chrome Extension: The Best Local Dev Testing Setup Right Now | Test-Lab.ai
- Creator
- Test-Lab.ai
- Published on
- test-lab.ai
- Original date
- Mar 14, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude Code
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.