How to give Claude Code hands in your browser

2 September 2026 · 7 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 so it works in every project.

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.

Step 3: verify

Start a new Claude Code session and ask it to list your open tabs. Under the hood it calls thedowser_tabs tool; if your tabs come back, everything is paired. Your five free days start automatically, no card.

What Claude Code can do with hands

• dowser_find: locate any element from plain English, "the newsletter unsubscribe link", in a few milliseconds, locally.
• dowser_act: click it, fill it, press keys in it.
• dowser_read: pull a compact outline or the readable text of the page.
• dowser_navigate and dowser_tabs: open pages, switch tabs.

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.

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, cancel) need explicit confirmation.
• If it is not confident which element you meant, it returns candidates instead of guessing.

Questions people ask

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 $29 once. No subscription; the license covers all your devices.

Two minutes from now Claude Code can click. Free for 5 days, $29 once after. Get Dowser.