← Back to library

Have Claude Code check its own UI work in your real Chrome

Test-Lab.ai's team used Claude Code with Anthropic's Chrome add-on daily for weeks. Because the extension shares the real browser session, the agent sees local servers, cookies and logins, then clicks through the interface and reads console output. They compare it with Playwright MCP, warn about token cost and suggest a subscription over metered API billing.

  • OutcomeLet the coding agent write a change, open your local app, click through it, read console errors and fix what broke in one session.
  • SetupMinutes
  • LevelIntermediate
  • CreditTest-Lab.ai
View original
Works with
Claude CodeClaude

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

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?

  1. Install and connectAdd the extension, then start Claude Code with its Chrome flag or the in-session command.
  2. Run your dev serverHave the app up on localhost so the agent can open it.
  3. Ask for change plus checkRequest the feature and a click-through of the affected screens.
  4. Have it check browser errorsThe agent picks up errors and fixes them before reporting done.
  5. 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.

Prompt0 variables
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?
It has more tools and cross-browser support, but the authors hit documented stability issues in daily use.
Is the author neutral?
They build a testing product and say so, framing it as a complement for full regression coverage.

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.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminWorkflow✓ AI dry run

Ask Reddit's experience before you pick a library

Let your coding agent search Reddit for long-term user reports on a library, an error message or a competitor before you commit to a choice.

Credit: u/karanb192 on r/ClaudeCode

Minutes
Operations & AdminPrompt✓ AI dry run

Give your agents one shared wiki that only one agent edits

Replace scattered agent memories with a single Markdown wiki in git: every agent reads a short daily brief from it, agents and scripts file sourced notes into an inbox instead of editing pages, one steward agent checks and merges those notes each morning, and private agent memory keeps only personal preferences.

Credit: Siim Tolk

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Make your coding agent's weekly usage last all week

Cut how much of your coding agent allowance each session burns by planning with a larger model, building with a smaller one, and handing off notes between sessions.

Credit: u/little_babushkaa on r/ClaudeCode

Under an hour
Operations & AdminWorkflow✓ AI dry run

Move self-hosted agent cron jobs to cloud scheduled tasks

A clear plan for which scheduled agent jobs can leave your server, which need reshaping, and which can simply be deleted.

Credit: u/jonathanmalkin on r/ClaudeCode

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Plan today across work tools with a read-only agent

Get one prioritized view of today's tasks, blockers and meeting prep drawn from all your tools, without the agent changing anything at the source.

Credit: Kim Maida

An afternoon+