Principles
It does not lie
about anything.
Browzie makes automation look like what it really is underneath, a careful session in a real browser, and removes the artificial tells that tools add.
- 22 of 22 footprint checks
- Nothing injected into pages
- Every CAPTCHA comes to you
Never, in any version
It never…
None of these exist anywhere in the code. There is nothing to switch on.
- 01changes the user agent, client hints or
navigator - 02touches WebGL, canvas, fonts, timezone, language or screen values
- 03patches page functions or uses stealth plugins
- 04uses proxies or rotates IP addresses
- 05runs headless against real sites
- 06solves, clicks into or bypasses a CAPTCHA or bot check
What it does instead: real input in your own profile, human-shaped timing, per-site rate caps, and a handoff to you whenever a site asks for a person.
Footprint
What a page can see.
A probe page records everything a detection script could read while Browzie works on it. The same checks run on every build, at the human pace.
npm run footprint
navigator.webdriverfalse- DevTools console-serialisation tellnot triggered
- Extension files reachable from the pageblocked
- DOM nodes or attributes added to the pagenone
- Untrusted input events0 of about 300
- Pointer path to the target30+ moves, curved
- Move event ratemedian about 12 ms
pressureon pointerdown0.5- Button held40 to 200 ms
- Pointer positions on the pixel gridall
- Every key has a down and an upyes
- Typing rhythmhuman
- Capitals typed with a real Shiftyes
- Keys only while the page has focusyes
- Text arrived exactlyyes
- Scrolling by whole wheel notchesyes
- Viewport resize while Browzie workednone
- The click arrived exactly onceyes
22 of 22 checks passed
Stated plainly
What remains observable.
-
Chrome’s debugging bar
“Browzie started debugging this browser” is shown to you. It is browser UI, not page content. A page that was already open when Browzie first attached sees one resize; pages Browzie opens do not. Cancel pauses Browzie.
-
A new window settling
The first page in a new Browzie window sees the window settle its size, as any page in a freshly opened window does.
-
Timing, not identity
A page can measure that the user is consistent and unhurried. That is the point. It cannot read anything that says “automation”.
-
evaluatein the main worldWith
world: "main"code runs in the page’s own world, where a page could notice it. The default is an isolated world, which leaves no trace. Avoid main on sensitive sites.
Bot checks
Every challenge goes to you.
Browzie checks every frame, through shadow roots, before every input action. It never moves into, clicks, reads or screenshots a challenge on purpose, and never calls a solving service.
- Before every input action
- Challenge visible in any frame? No
- Act
- Before every input action
- Turnstile on the page
- Wait up to 8 s for it to pass by itself
- Still there? No
- Act
- Still there after 8 s: it goes the other way →
- Before every input action
- Challenge visible in any frame? Yes
- Stop input on this tab
- Banner on the page, notification with Done
- The tool returns
HUMAN CHECKto Claude - Claude calls
handoffand waits - You solve it. Gone for 1.5 s, or you click Done
- Claude continues with a fresh snapshot
handoff is also the tool for anything else that needs you: two-factor codes, payments, permissions. Snapshots show ! HUMAN CHECK on this page, so the model knows before it tries.
Working beside you
You always win.
- It never takes the focus. Keep working in other windows. The focus never moves, and Browzie carries on behind you.
- Your click wins within one event. A click, wheel turn or key in the Browzie window stops the current action and hands you control.
- One pointer per page. While your pointer rests over its window, Browzie waits, then re-plans from where the page last saw a pointer, so the page never sees a jump.
- Pause any time. The toolbar button pauses and resumes everything. Cancel on Chrome’s debugging bar pauses too.
BROWZIE_YIELD=any restores the strict rule: any input anywhere stops Browzie.
You clicked or typed in the Browzie window, so Browzie stopped this action and gave you control.
Click inside the window to take over
Security model
Nothing listens on the network.
The pipe is local and per user, and needs a 192-bit token from a file only your Windows account can read.
Only the extension with Browzie’s pinned id can start the native host.
The extension exposes nothing to pages: no web-accessible resources, no message listeners for pages, no content scripts outside the tabs it drives.
It can do whatever you can do in that browser profile. Treat it like any tool that has your logged-in browser.
Per site, per minute
human
fast
Anything over the cap waits. It never errors.
The honest limit
No tool can guarantee that an account is never flagged. Some sites forbid automation in their terms, regardless of how it looks.
Browzie reduces the risk by behaving like a careful person in your own browser, and by stopping whenever a site asks for a human. Use it where you are allowed to.
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.