Pricing
The plugin and helper are open source under MIT. The native PairBrowse browser is free for personal, non-commercial use. A Pro license for commercial use is on its way.
Claude Code
Codex$0
For personal and non-commercial use.
Pricing soon
For teams and commercial use.
Write to us and we will tell you when Pro opens.
The fully open setup is fine for commercial use. Set one value in ~/.pairbrowse/config.json and PairBrowse runs on an open Chromium build instead of the native browser. The plugin is MIT and the open Chromium builds keep their own open-source licenses.
"browserEngine": "auto"
Native PairBrowse browser on macOS and Linux x64. Free for personal, non-commercial use; commercial use needs Pro.
"browserEngine": "chromium"
Fully open setup. Fine for commercial use.
Compare
| Feature | Free | Pro Coming soon |
|---|---|---|
| Price | $0 | Pricing soon |
| Plugin and helper source (MIT) | Included | Included |
| Works with Claude Code and Codex | Included | Included |
| Shared sessions, join codes, named cursors | Included | Included |
| Hand-offs and guarded clicks | Included | Included |
| Fully open Chromium setup, commercial use included | Included | Included |
| Native PairBrowse browser, personal non-commercial use | Included | Included |
| Native PairBrowse browser, commercial use | Not included | Included |
| Ready-made native builds and updates for commercial use | Not included | Included |
| Native build source and pipeline access | Not included | Included |
| Contribute to the native build | Not included | Included |
Scroll the table sideways to see both plans.
The plugin and helper are, under the MIT License; the source is on GitHub. The native PairBrowse browser is a closed Chromium build, free for personal, non-commercial use under its own binary license. Third-party components inside it, such as Chromium, keep their own licenses and the rights they give.
If you want everything open, set "browserEngine": "chromium" and PairBrowse runs on an open Chromium build instead.
Yes, today, with the fully open setup: set "browserEngine": "chromium" in ~/.pairbrowse/config.json. The plugin and helper are MIT, so commercial use is fine.
Commercial use of the native PairBrowse browser needs a PairBrowse Pro license or written permission. Pro is coming soon; ask to be notified.
Commercial use of the native PairBrowse browser, ready-made builds and updates, and access to the native build's source and pipeline, where Pro members can also contribute. Pricing is not set yet.
The browser runs on your computer and is driven over a private pipe, with no debugging port; the only way in is a socket file that only your user account can open. Everything in ~/.pairbrowse is private to your user.
Clicks are checked on your computer. No other model or service judges a click, and nothing about a click leaves the computer. Your agent sees what it reads from the page, with saved passwords masked.
The live view listens on 127.0.0.1 only. When you share a session with a join code, the traffic goes through a Cloudflare Quick Tunnel, and only after you allow each person in. Tabs and form values travel; cookies, logins and passwords never do, and sensitive fields such as card numbers cross only as "filled" or "empty".
The full threat model and its limits are in docs/security.md.
Claude Code and Codex, each through its own plugin. A teammate's Claude or Codex can work in another tab of the same session.
Other MCP clients can drive the browser too. Because those apps can't be relied on to ask you, the helper applies the safety rules itself and hands final actions such as pay, delete or publish back to you.
Install the plugin, give your agent a web task, and invite your team in.