Handoff
The agent drafts. You decide.
PairBrowse stops at the steps that need a person and hands them to you in the same tab. Step in whenever you like: the agent waits, then takes a fresh look and carries on.
PairBrowse Step in any time
Type, and the agent waits.
Click or type in the agent's tab and its next action there waits until you have stopped for two seconds. Then it is told what you did, which button or field, never what you typed, and looks at the page again before going on.
Pause agents, in the bottom bar and the side panel, stops every agent before its next browser action. Only people resume: there is no tool for it, and messages asking for it change nothing.
- Moving the mouse or scrolling holds nothing up.
- A field you fill stays yours for two minutes.
- Old element references are refused after you change the page.
- Pause agents stops them all until a person presses Resume.
Your turn
Logins, 2FA, CAPTCHAs and payment come to you.
When the agent reaches a sign-in, a 2FA code, a visible CAPTCHA or bot check, or a payment, the badge says Your turn with what to do, and PairBrowse sends you a notification. You finish the step in the same tab.
The agent waits and continues by itself once the page moves on, for up to about ten minutes. If it is missing a legal, tax, address or bank detail, it asks for all of them at once.
PairBrowse never solves CAPTCHAs or bot checks, and doesn't use solving services.
Guarded clicks
Real commitments ask first. Ordinary steps don't.
Payments, danger buttons and deletions are found from the page's structure, not its words: card fields, payment frames, danger styling, a delete method. The agent names the other final actions it knows from its task, like publish, send or submit, and every named click asks you.
No other model or service judges a click, and nothing about it leaves your computer. In Codex and other apps that can't ask, those clicks are refused and handed to you.
Pre-submit reviews. Submit for review and Publish stay blocked until the agent has checked the listing against the platform's current official requirements and recorded a passing review. Then it still asks you. This can't be turned off.
Passwords
Passwords by name. The model never sees them.
The agent types a secret's name. PairBrowse fills the real value, checked against the real address of the tab by the helper, not by the agent. A page that tries to talk the agent into typing it elsewhere gets nothing.
- Saved from the Profile panel into a file only you can read.
- Each password works only on the HTTPS sites you list for it.
- Masked in everything the agent reads back.
- No screenshot is sent while a saved password shows on the page.
Let the agent draft. Keep the final say.
Install the plugin in Claude Code or Codex, ask for a web task, and watch it work in a browser you can step into.
NextShare your dev server