How to give Claude Code hands in your browser

2 September 2026 · 10 min read · by Akhil Gorantala

Claude Code can already read your repo, run your tests and edit your files. The browser is usually where its reach ends: it can tell you what to click, but not click it. This guide wires that last gap with Dowser, our extension plus local MCP server, and takes about two minutes. By the end, "cancel my Figma trial" or "add this to the cart and stop at checkout" are things Claude Code just does, in your own browser, while you watch.

What you need

• Claude Code installed and signed in (any plan, including free).
• A Chromium browser: Chrome, Brave, Edge or similar.
• Node.js 18 or newer (node -v to check).

Step 1: hand Claude Code one line

Paste this into a Claude Code session:

Set up the Dowser browser extension for me: fetch https://dowser.click/install.md and follow the steps in it, then confirm Dowser is connected.

That URL is a setup guide written for agents, not people. Claude Code fetches it, downloads the Dowser folder to your home directory, runs the pairing step (which mints a secret on your machine, shared with nobody), and registers the MCP server under your user account with claude mcp add --scope user, so it works in every project rather than just the current folder. You can read the whole guide yourself first at dowser.click/install.md; it is short and there is no magic in it.

Step 2: the one click that must be yours

Browsers do not let a program install an extension, which is the right rule. Claude Code will ask you to add Dowser to your browser; you press the button, and that is your whole job. If the Chrome Web Store listing is not available in your region or browser, the guide falls back to loading the extension unpacked from the downloaded folder: chrome://extensions, Developer mode on, Load unpacked, pick the dist folder. Either path ends in the same place.

Step 3: verify

Start a new Claude Code session and ask it to list your open tabs. Under the hood it calls the dowser_tabs tool; if your tabs come back, everything is paired. Your five free days start automatically, no card. A freshly installed extension can take up to 30 seconds to pair on its first connection, so if the first try says not connected, wait half a minute and ask again.

What Claude Code can do with hands

• dowser_find: locate any element from plain English, "the newsletter unsubscribe link", in a few milliseconds, locally, in any language the page speaks.
• dowser_act: click it, fill it, press keys in it; selects take the option label.
• dowser_read: pull a compact outline or the readable text of the page, sized for a context window rather than a raw dump.
• dowser_navigate and dowser_tabs: open pages, switch tabs, route actions to the tab you meant.

The part that makes this practical is what does not happen: no screenshots, no page snapshots shipped into your context window, no model call to find a button. Finding runs on a local ranker against the page's accessibility tree, so a three-click task costs Claude Code three sentence-sized tool calls and single-digit milliseconds each. How that compares with the snapshot-driven alternatives, with measured numbers, is in the Claude extension comparison.

Guardrails worth knowing

• Every action shows a visible cursor and highlight, so you always see what it is doing.
• Move your mouse and it steps aside instantly; you always win.
• It refuses password, card and OTP fields outright, and destructive clicks (delete, pay, transfer, cancel) need explicit confirmation.
• If it is not confident which element you meant, it returns candidates instead of guessing.
• Everything runs against 127.0.0.1; the extension has no server of ours to talk to.

Five workflows to steal

The post-deploy click-through: "open staging and walk the signup flow, tell me what breaks." Claude Code navigates, fills, clicks and reports, on the real page.

The subscription audit: "go through my open tabs and find every page with a recurring charge mentioned." dowser_read across tabs, no copy-pasting.

The form slog: conference registrations, vendor onboarding, address changes; say the details once and watch them land. The deep version of this is the form-filling guide.

The comparison shop: "open these three product pages and build me a table of price, warranty and shipping."

The unsubscribe sweep: "open this newsletter's unsubscribe link and finish the flow, but show me before any final confirm." The confirmation guardrail makes this safe to delegate.

Troubleshooting

• "Extension is not connected": check the extension is enabled at chrome://extensions and the browser is open; then start a new Claude Code session and try again after 30 seconds.
• Setup ran in the wrong folder: the MCP server and the pairing secret must come from the same downloaded folder; rerun npm run setup in it if unsure.
• Store install shows "Not paired": run npm run setup again and restart the browser; the pairing helper answers on the next launch.
• Corporate browser blocks the store: use the unpacked path from step 2; identical functionality.

FAQ

Does this work in every project?

Yes. The setup registers the MCP server with --scope user, so Dowser is available wherever you run Claude Code, not just the folder it was installed from.

Can I use it alongside Playwright MCP or other browser tools?

Yes, they are independent servers; many people keep Playwright MCP for tests and Dowser for live tasks. Our comparison covers when each fits.

What does it cost?

Five days free with everything on, then $19 a month, cancel anytime; the license covers all your devices, and the first payment is refundable within 14 days if it is not for you.

Does my browsing data go to Dowser's servers?

There are no Dowser servers in the loop. The extension talks only to the MCP server on your own machine, and page content is processed locally. The site's privacy page spells it out.

Claude Desktop instead of Claude Code?

Works too: add the server to claude_desktop_config.json; the exact snippet is in the install guide, along with Cursor, Windsurf, Codex CLI and Gemini CLI.

What if Claude clicks the wrong thing?

Low-confidence finds return candidates instead of acting, destructive actions require confirmation, and everything visible happens under a cursor you can interrupt by moving your own mouse. In practice the failure mode is "it asks", not "it guesses".