Skip to content
agentusehub

Test local web apps and fix errors in one session

Claude Code with Claude in Chrome writes code, opens localhost, clicks through the UI, reads console errors and fixes them without the developer touching the browser.

Time saved
Not reported
Setup time
Not reported
Running cost
Not reported
Cost range
Not reported

Use case overview

Claude Code with Claude in Chrome writes code, opens localhost, clicks through the UI, reads console errors and fixes them without the developer touching the browser.

Reported experience

  1. What they did

    The Claude in Chrome extension is connected to Claude Code with `claude --chrome` or `/chrome`. It shares the developer's real Chrome session, including logins, and new domains need approval once. Asked to add a dashboard table filter, Claude wrote the component, opened the page and tried the filter. It spotted that the URL query params weren't updating, fixed the router logic, and confirmed the fix with a reload.

  2. How it went

    The filter example took three iterations with no browser work from the developers. The setup is limited to a developer's own workstation: it needs a visible Chrome window, so no CI or headless runs, and it works in Chrome and Edge only.

  3. Worth knowing

    Browser interaction uses a lot of tokens, about 7.7% of context per interaction. The authors call API pricing a money pit and say a Max subscription is needed for heavy use.

Example prompts

Try with Claude Code
Start my app locally with [start command], then open it in Chrome at [localhost URL] and click through [feature or flow]. Read the browser console and network errors, find the cause in the code, and fix it. Repeat until the flow works with no console errors. Then summarize what you changed. Don't commit or push anything without asking me.
Software & DevOps

Port a Chrome extension to Safari

The author had ChatGPT take the Session Buddy extension source from Chrome, port it to Safari and install it, taking about 20 minutes.

ChatGPT