Trust boundaries first.
BrowserPair separates the user, agent key, cloud control plane and extension executor so no single untrusted page or agent response can silently expand authority.
Content from a website can inform the task, but it cannot add permissions or override the task contract.
Browser mutations happen only inside the extension executor. Cloud coordinates the task but does not click, fill or navigate pages itself.
Hosted tasks act only on strongly owned tabs. Probable or unrelated tabs require explicit input instead of silent adoption.
Keys define the ceiling.
Each agent key can restrict browser IDs, domains, ordinary capabilities and elevated capabilities. The immutable task contract narrows that scope again for one task.
Browser scope
Choose which connected browser identities an agent can use.
Domain scope
Limit the websites a key or task may navigate and act within.
Capability scope
Grant only the action classes the agent actually needs.
Approval policy
Choose when BrowserPair pauses for a person without expanding hard scope.
Sensitive operations get extra friction.
Publish, send, delete, payment, password and transfer effects require explicit capability and any confirmation required by policy or the task contract.
Passwords, OTPs, card data, API keys and auth tokens are redacted on-device by default. BrowserPair discloses a protected category only after an explicit user grant scoped to the effective task, agent and domain; one-time grants are bound to the exact pending action.
Agent keys and browser device credentials are separate. The extension does not store the agent key that authorized a task.
Unknown effects are not retried blindly.
Browser automation can fail at awkward boundaries: the page may change, the network can disappear or a tab can reload after a click. BrowserPair records task and effect state so recovery can distinguish “safe to retry” from “must verify first.”
Retrying the same task creation request does not create duplicate work when the idempotency key and body match.
Controllers and reconnects carry generations so stale executors cannot keep mutating a task they no longer own.
An executing or unknown side effect is verified before retry. If certainty is impossible, BrowserPair waits for resolution.
The cloud coordinates; the extension mutates.
BrowserPair Cloud handles identity, permissions, routing, usage, audit and optional hosted Brain/Reflex coordination. Semantic observations may transit the cloud and a user-selected model provider when a task needs them; bounded DOM, accessibility data or screenshots are sent only when the configured observation policy permits the requested mode. Your signed-in browser profile and browser mutation authority remain on the connected device.
Task goals, contracts and results stored by BrowserPair are encrypted at rest. Operational logs are designed to avoid task/page text, cookies and credentials.
For security questions or responsible disclosure, email browserpair@gmail.com.