Work in one live browser with your AI agent and your team. Claude Code or Codex drives the tabs, teammates join from their own computers with their own cursor and their own agent, and you step in whenever you like. Sites see an everyday browser, not an automated one.

pairbrowse.com

• Built for working together. Send a watch or drive code: a teammate sees the same tabs live, clicks and types with their own cursor, and their Claude or Codex can work in another tab of the same session. Pause every agent at once with one click.
• Watch live by link. Copy a watch link in one click (or send /watch to your Telegram or Discord bot): anyone you give it to watches the browser live from any browser or phone, view only, with card and password fields covered, until it expires or you stop it.
• Stealth browser with a real fingerprint. A hardened browser driven through Patchright instead of stock Playwright: no automation flag, AutomationControlled off, no debugging port. On a Mac the fingerprint is captured from your own machine and kept per profile, so the GPU and WebGL it reports, time zone and language match real hardware. Clicks and typing follow human timing and curved mouse paths. Fewer CAPTCHAs, fewer "unusual activity" blocks.
• Fast, accurate forms. Fast mode fills a whole page (fields, dropdowns, checkboxes, Next) in one action from the page's accessibility tree, then checks a screenshot for what the tree can't show. Remembered details mean no retyping; Pay, delete, publish and send still wait for you.
• Separate from your everyday browser, but it remembers. Logins persist in their own profile, one per client if you like. Passwords are filled only on the sites you allow and never shown to the model. Half-finished jobs resume tomorrow.

claude plugin marketplace add pairbrowse/pairbrowse
claude plugin install pairbrowse@pairbrowse

Restart Claude Code. Needs Node.js 20+ and Claude Code running on your computer (not a cloud session). Codex: see docs/codex.md. Grok uses the Claude Code install as it is: see docs/grok.md. Update, uninstall and a local checkout: docs/install.md.

PairBrowse runs in the native PairBrowse browser (the default on a Mac, Apple Silicon or Intel, and on Linux x64): a hardened browser made for PairBrowse, with its own tab strip, docks, new tab page and Settings built in, and pointers of the people who joined drawn by the browser itself. It looks like an everyday browser to sites, so you see fewer CAPTCHAs, and it is the only browser PairBrowse runs on a server.

PairBrowse as an extension is the fallback, for Windows until the native browser arrives there and for people who don't want the native browser: the same plugin and pages, loaded into another browser (a pinned build on macOS, Playwright's browser elsewhere, or one of your own), with a side panel (Cmd+Shift+Y, Ctrl+Shift+Y off a Mac) in place of the docks. It lacks server mode, the engine's identity work, humanized input, and the WebGPU and proxy patches, so sites block it more often.

Pick one with "browser" in ~/.pairbrowse/config.json: "pairbrowse" (the native browser) or "pairbrowse-open" (PairBrowse as an extension; the older "chromium" still works); PairBrowse asks once, and Settings can switch it. Details: The browser.

Register a Shopify Partner account for our company and start an app listing for our app.

The first run downloads the browser (about 150 MB) and opens it. Sign into the sites you need once; they stay signed in.

Invite a colleague to watch or co-drive, or share one browser between two computers with a join code (pairbrowse_invite, pairbrowse_join). Out of the box the connection goes through a free Cloudflare Quick Tunnel: no account, a random address each time. If you would rather use your own address and account, set it once in ~/.pairbrowse/config.json and everything else stays the same:

"sharing": { "tunnel": { "kind": "ngrok", "authtoken": "...", "domain": "share.example.com" } }

kind can be quick (the default), cloudflare (a named tunnel with your token and hostname), ngrok, tailscale (Funnel) or command (any program that prints a public URL). Your token stays in that file and goes only to the provider's own program. Setup for each is in Working together.

Use the built-ins for a quick task in a site you're already signed into. Use PairBrowse for doing it together, long form work, sites that block automated browsers, or client accounts kept apart.

• No debugging port: the browser is driven over a private pipe, reachable only by your user.
• Pay, publish, delete, send and submit-for-review clicks ask you first; you can answer in the PairBrowse window or the terminal. Payments, danger buttons and deletions are found from the page's structure (card fields, payment frames, danger styling, HTTP DELETE), not its words; Claude or Codex names the other final actions from its task. Ordinary steps (Continue, Save, Next) don't interrupt you, and nothing is sent to another model or service. Publishing also needs a passing check against the platform's current rules.
• Passwords work only on the domains you list for them and are masked in everything the model reads.
• Join codes share tabs and form values, never your cookies, logins or passwords, and only after you click Allow.
• PairBrowse never solves CAPTCHAs or bot checks.

Full threat model and limits: docs/security.md. Report issues privately: SECURITY.md.

Quick sign-ups, registrations and listings that come up while you build a product (developer accounts, app store listings, API keys, store settings), with you in the loop. Not for creating accounts in bulk, getting around a site's bot checks, or anything else a site doesn't allow. You use it on your own accounts and accept each site's terms.

• The plugin (this repository) is MIT: LICENSE.
• The native PairBrowse browser is a private binary under BINARY-LICENSE.md: free for personal, non-commercial use; commercial use through PairBrowse Pro.
• PairBrowse as an extension is the same MIT plugin, loaded into another browser under that browser's own license.

• What it does: features, how a run goes, design principles
• Install, Codex and Grok
• The browser: where you see it, the desktop app pane, the native build
• Using PairBrowse: remembered details, passwords, sessions, fast mode, popups, uploads
• Working together: invites, join codes, several agents on one browser, your own tunnel
• Running on a server: which computer, the service, the virtual screen, hand-offs to your phone
• Browser profiles: a session's settings, import and export, checking a profile
• Skills
• Configuration
• Troubleshooting
• Security, the assurance case and reporting a vulnerability
• Architecture
• Development
• Changelog and Roadmap

Early development. Expect breaking changes while the helper, collaboration model and agent integrations evolve, and treat the security model as still maturing.