The PairBrowse browser
A browser that looks like yours.
A Chromium build made for agents working in a real, logged-in browser. Automated browsers often differ from everyday ones in ways sites notice. The PairBrowse browser keeps those differences out, so sites see a normal browser.
Compatibility hardening
The everyday browser, minus the automation differences.
Automated browsers often differ from everyday ones in ways sites notice. The native PairBrowse browser keeps those differences out, while still running in the same visible window you and your agent share.
It keeps its logins in its own profile, so after switching to it you sign in to your sites once more.
- Launches without the automation flag.
- Chromium's AutomationControlled feature is off.
- Driven through Patchright, the default browserDriver.
- Time zone and language follow your system.
- WebRTC doesn't reveal your local addresses by default.
Fingerprint
Captured once, from your own Mac.
On a Mac, the browser's fingerprint is captured from your own Mac, so it stays coherent with the real machine. The capture runs once per Mac in a hidden browser on the real GPU and is saved per profile.
It is kept in a private ~/.pairbrowse/mac-host-profile.json until the browser version or hardware changes. On Linux, the browser runs with a fingerprint seed kept per profile instead.
Human-like input
Human-like input, when you want it.
Optional, and off by default, so actions stay deterministic for testing. Turn it on and every action the agent takes in the native browser follows one human input style.
- Eased, slightly curved mouse paths.
- Key-by-key typing with human timing.
- Moving, clicking, dragging, scrolling and typing in one style.
- All as native trusted input.
Pinned and verified
Checked before it runs, with a way back.
PairBrowse picks the build for your platform and chip and downloads it once from its public GitHub release. It checks the SHA-256 pinned in the open source plugin, the build manifest, on macOS the signature, then runs a launch test, and keeps the previous version for rollback.
The small engine pack the browser launches with is checked the same way, before every load.
Platforms and license
Free for personal use. Fully open when you need it.
The native browser runs on macOS (Apple Silicon or Intel) and Linux x64. A Windows x64 build follows; until then PairBrowse uses Playwright's Chromium on Windows.
The browser binary is free for personal, non-commercial use. For commercial use, get PairBrowse Pro (coming soon), or set "browserEngine": "chromium" for a fully open setup on an open Chromium build. With it, PairBrowse removes the automation flag and turns off AutomationControlled. That stops basic navigator.webdriver checks, nothing more.
The plugin and helper stay MIT either way.
Try it on your next form.
Install the plugin in Claude Code or Codex, ask for a web task, and watch it work in a browser you can step into.
NextAll features