Browzie for Claude Code
Hands off. Eyes on.
Browzie lets Claude Code use your everyday Chrome the way you do: a cursor you can watch, real clicks and keystrokes, and the logins you already have.
4 results for “quiet, good wi-fi”
Nineteen tools, one cursor
Everything your hands do in a browser.
Each tool is a move you would make yourself, set out here like the elements of a table. Point at one to watch it work.
- 19
- moves
- 6
- groups
- 10
- load up front
Pages
navigate
Open a URL, go back, forward or reload, or open a new tab. Returns a snapshot.
navigate {url: "acme.example/jobs"}
snapshot of the new page
Open a URL, go back, forward or reload, or open a new tab. Returns a snapshot.
Compact page text with refs like [e12], instant, with no input sent.
Search every frame by text, name, role or CSS selector and get refs.
Readable text of the page or of one element, with paging.
The viewport in CSS pixels, optionally with ref labels drawn on.
Move the visible cursor to an element and click with real mouse input.
Rest the cursor on an element to open hover menus and tooltips.
The mouse wheel, by amount, to an edge, or until a ref is in view.
Many fields at once: text, checkbox, radio, select, date, slider and file inputs.
Answers the file chooser a button opens. The Windows dialog never appears.
Real keystrokes. Long text goes in word chunks and can resume.
Keys and shortcuts such as Enter, Escape or Control+A.
Text, a selector, a URL, their disappearance, or a button becoming enabled.
List, open, switch and close Browzie’s tabs and followed popups.
Accept or dismiss alert, confirm and prompt dialogs.
Hands control to you and waits: CAPTCHA, two-factor code, payment.
You pick a saved login in Chrome’s own list. Browzie presses the button.
JavaScript in an isolated world by default, which leaves no trace.
Several steps in one call, so a whole flow takes one model turn.
Speed
Fast where it counts.
A zero-dependency chain of stdio, a named pipe and native messaging. Pages arrive as compact text instead of screenshots, and batch runs a whole flow in one model turn.
2ms
round trip through every hop
Text, not pixels
A snapshot reads the page before a screenshot is half done.
snapshot
4 ms
screenshot
58 ms
Nothing listens on the network
Every hop is local. 2 ms there and back.
- Claude Codeyour claude.ai loginMCP over stdio
- MCP serverserver/server.jsnamed pipe + token
- Native hosthost/host.jsnative messaging
- Extensionsw.js + agent.jstrusted input
- Your Chrome tabreal input events only
2ms round trip through every hop
Measured with npm run bench: headless Chrome for Testing, local pages, medians of 15 runs.
snapshot4 ms
[e3] link “Hacker News”
[e5] link “login”
[e9] link “Show HN: a tiny pixel font”
[e12] link “Ask HN: what are you reading?”
[e30] textbox “Search”
after click [e5]diff
+ [e31] heading “Login”
+ [e32] textbox “username”
− [e5] link “login”
notes.md, your windowhas the focus
1 Trip plan
2
A cursor you can watch
A native overlay draws a purple arrow exactly where Chrome receives the pointer, with a ripple on every click and a thin frame around the page in use.
Reads pages as text
Compact snapshots with refs like [e12] instead of pictures, across frames and shadow roots. After each action Claude gets only what changed.
CAPTCHAs come to you
Bot checks are detected in every frame. Browzie stops, shows a banner, notifies you and waits. It never solves, clicks or works around a challenge.
Works beside you
It never steals the focus, so you keep working in other windows. Click or type in its window and it hands control back to you at once.
Browzie makes it human
Built around how you browse, not how bots do.
Sign in
EmailSaved logins
you@example.com••••••••••
work@example.com••••••••
batch1 model turn
navigateshop.example.com
fill3 fields
click“Continue”
wait_for“Order placed”
4 steps · 4 lines back · full result of the last
Real input, human shape
Trusted events through chrome.debugger: curved Fitts’ law movement, separate button and key down and up events, Shift as its own key, whole wheel notches.
Pick the pace
fast for a quick, confident user, brisk for a practised one, human for a careful person with natural pauses and typos that get corrected. Try it on the left.
Passwords stay yours
signin clicks into the form so Chrome lists your saved logins. You pick one in Chrome’s own list and Browzie presses the button. It never types, reads or sees a password.
A whole flow, one turn
batch runs several steps in one call, and input tools return only what changed on the page. Claude spends its turns thinking, not waiting.
Your browser
stays yours.
Nothing is injected into the page, nothing listens on the network, and the user agent, fingerprint and IP are never touched. Bot checks always come to you.
Read the principlesEvery claim has a test
Measured, not promised.
The claims on this site come with a command you can run yourself. Pick one and watch it run.
6/6
real sites in a visible window
bot.sannysoft.com checks passed
WebDriver, as sannysoft sees it
deviceandbrowserinfo.com, “are you a bot”
Wikipedia search, preview opened by the hover
navigator.webdriver
untrusted input events
DOM nodes or attributes added to the page
pointer path to the target
pressure on pointerdown
pointer positions on the physical pixel grid
capitals typed with a real Shift
keys only while the page has focus
position 1, overlay tip vs real pointer
position 2, overlay tip vs real pointer
position 3, overlay tip vs real pointer
session window and popup placed there and restored
your foreground window and desktop, also while you type
the popup does not take your view along
page visible and focused
clicks and typing reach it
a sentence typed to the end while another window had the focus
the focus
every key reached a focused page
typing in the Browzie window
motion and timing model
every form field type
same-site, cross-site and nested iframes
closed shadow roots
bot-check refusal and handoff
two concurrent sessions
FAQs
Good questions.
Questions
Answer
Does Browzie need an API key?
No. Claude Code’s own login is the model, and Browzie never calls a model itself. Your Chrome profile is the browser identity, so there is nothing to configure.
No. Claude Code’s own login is the model, and Browzie never calls a model itself. Your Chrome profile is the browser identity, so there is nothing to configure.
Browzie never changes the user agent, navigator, WebGL, canvas, fonts, timezone or IP, and nothing is injected into pages. A page sees real, trusted input with human timing. Still, no tool can promise an account is never flagged, and some sites forbid automation in their terms, so use it where you are allowed to.
Bot checks are detected in every frame. Browzie stops input on that tab, shows a banner, sends you a notification and waits. Solve it, or click Done, and Claude carries on with a fresh snapshot. It never solves or clicks a challenge.
Yes. Browzie never takes the focus, so your typing in other windows is untouched. Click, scroll or type inside the Browzie window and it stops the current action at once and gives you control.
No. With signin, Chrome lists your saved logins and you pick one in Chrome’s own list. Browzie only presses the button afterwards. It never types, reads or shows a password, not even its length.
Yes. Any client that speaks MCP over stdio can use it: point it at node <path>/Browzie/server/server.js. The installer’s --no-mcp flag skips the Claude Code registration.
Browzie sends trusted input through chrome.debugger, and Chrome shows that bar so you always know. It is browser UI, not page content. Clicking Cancel there pauses Browzie.
Windows 10 and 11 today, with Node.js 20 or newer and Google Chrome. macOS and Linux overlays are on the roadmap; the native host already handles Unix sockets.
Ready when you are
One browser.
Now, two cursors.
Clone it, run one installer, load the extension once, then ask Claude to open a page. You will see the purple cursor on its way.