Claim·Claude Code, Claude in Chrome·Software companies
Local browser testing loop
Claude Code with the Chrome extension builds features, then opens localhost in the author's real Chrome session to test, read console errors, and fix issues.
On a dashboard filter task, Claude fixed URL query param handling in three iterations without the author touching the browser.
Overview
How it was set up
Claude Code (or Claude Desktop) connected to the Claude in Chrome extension via `claude --chrome` or `/chrome`. It shares the real Chrome session with approved domains.
Worth knowing
Heavy browser use burns tokens fast; the author says a $200/month Max plan is effectively required. No CI or headless support, Chrome and Edge only.
A prompt to start from
The source does not show the prompt.
Sources 1
History
- Source published
- 2026-03-14
- Added to Agentic Feats
- 2026-10-13
- Pick
- No
- Markdown copy
- /c/local-browser-testing-loop-claude-code.md
More in software companies
15 featsResultSmall scoped fixes took about five minutes to test and merge versus roughly an hour by hand; the full-stack task failed and was rewritten.
ResultDevin found nearly every old term in a docs-wide rename, but the edits still needed 20+ manual commits.
ResultThe author shipped 120 models, an MCP server for Claude Desktop, and 140 chaos tests with a 100% pass rate over 22 months.