Browzie 0.1 is open source: MIT licensed, made for Windows 10 and 11.

Read the design
GitHub

Setup

Three commands.
One click.

The installer builds everything on your machine, downloads nothing, and registers Browzie for your Windows account only. Then you load the extension once.

  • Windows 10 or 11
  • Node.js 20 or newer
  • Google Chrome
  • Claude Code CLI
01

Clone it and run the installer.

Open a terminal in the folder you want Browzie to live in.

> git clone https://github.com/theyashdhiman04/Browzie.git
> cd Browzie
> node scripts/install.js

  • Builds the cursor overlay with csc.exe, the compiler that ships with Windows. Nothing is downloaded.

  • Registers the native messaging host for your Windows account only (HKCU).

  • Adds the MCP server browzie to Claude Code (user scope).

Terminal
> git clone https://github.com/theyashdhiman04/Browzie.git Cloning into 'Browzie'... > cd Browzie > node scripts/install.js okbuilt the cursor overlay lens\browzie-lens.exe okwrote the native host manifest (only extension jnpofggaaghogojkmhfmmlmgbdhlecae may start it) okregistered the native host for chrome (HKCU\Software\Google\Chrome\NativeMessagingHosts\com.browzie.bridge) okadded the MCP server "browzie" to Claude Code (user scope) Last step (once): load the extension into your everyday Chrome   1. open chrome://extensions   2. turn on "Developer mode" (top right)   3. "Load unpacked" -> C:\Users\you\Browzie\extension
02

Load the extension once.

In your everyday Chrome, not a separate profile. Browzie works in the browser you are already signed in to.

  1. 1

    Open chrome://extensions

  2. 2

    Switch on Developer mode, top right

  3. 3

    Click Load unpacked and pick the extension folder

Only this extension, with its pinned id, is allowed to start the native host.

Extensions
chrome://extensions
Extensions Developer mode
Load unpacked Pack extension Update
Browzie for Claude Code0.1.0ID: jnpofggaaghogojkmhfmmlmgbdhlecae

Select the extension directory

This PC › Users › you › Browzie

  • assets
  • extension
  • host
  • lens
  • scripts
  • server
  • test
CancelSelect Folder
You
03

Restart Claude Code and ask.

Claude now has nineteen browser tools. Ask in plain words, for example:

Use browzie to open news.ycombinator.com and tell me the top 3 stories.

A Browzie window opens beside your work, in its own purple tab group, and Claude answers from what it reads.

claude
> Use browzie to open news.ycombinator.com and tell me the top 3 stories. browzie · navigate url: "news.ycombinator.com" └ a snapshot of the page, with refs like [e12] Here are the top 3 stories:

What you will see

Five things tell you it is Claude.

Keep at least part of the Browzie window visible, snapped beside your work or on a second screen. Chrome treats the pages of a fully covered window as hidden, and a hidden page receiving clicks is something no person can do, so Browzie waits and tells you.

Commands

Check it. Undo it.

Everything the installer does can be checked step by step, and undone with one flag.

  • npm run check

    Diagnoses an installation step by step.

  • node scripts/install.js --remove

    Undoes everything the installer did. Remove the extension from chrome://extensions yourself.

  • node scripts/install.js --no-mcp

    Skips the Claude Code registration, for other MCP clients.

  • Any MCP client that speaks stdio

    node <path>/Browzie/server/server.js

    If claude mcp add fails during install, add it yourself: claude mcp add browzie -s user -- node <path>\server\server.js

If something is off

It tells you what to fix.

Failures come back as plain sentences with the fix, not stack traces. The native host logs to %LOCALAPPDATA%\Browzie\host.log.

> npm run check Browzie check   ok   cursor overlay built   ok   native host registered for Chrome   ok   host launcher C:\Users\you\Browzie\host\browzie-host.bat   FAIL no browser connected: is Chrome open with the Browzie extension enabled?   ok   MCP server registered and starts
Chrome is closed
The next tool call starts Chrome normally, without flags, and waits for Browzie.
Chrome is open without the extension
A clear message with the fix. npm run check diagnoses each step.
You reloaded the extension
Pending calls fail with “call the tool again”. The next call reconnects, and sessions and their windows come back.
The Browzie window is fully covered
Its pages are hidden to Chrome, so Browzie waits, up to 90 s with a notification, instead of clicking a hidden page.
A site asks for a person
Input stops on that tab and Claude calls handoff. Solve it, or click Done, and it carries on.

Before you start

Know what it does, and won’t.

01 How it works From a sentence to a click: the five pieces and the control loop behind every action. 02 Tools All nineteen tools, the ten Claude always has, and the three paces. 03 Principles What it never does, what a page can still see, and why you always win the mouse.