BrowserPair Quickstart: Connect a Browser and Run a Task

Go from a fresh BrowserPair account to a real browser task. The browser connection is shared by both product paths; after that, choose whether BrowserPair coordinates the Brain or your external agent does.

1. Connect

Pair the Chrome profile you already use.

2. Bound

Define exactly which browser, websites, and actions are allowed.

3. Run

Start from the dashboard, Remote MCP, or REST.

Connect your browser

Install BrowserPair

Add the BrowserPair extension to the Chrome profile you want to use for agent work.

Start pairing

Open the extension and choose Connect BrowserPair.

Approve the browser

Complete the pairing approval in the BrowserPair app.

Confirm presence

Open Browsers in the dashboard. The profile should show Online while the extension is connected.

BrowserPair uses the browser profile that is already signed in. You do not export the profile, cookies, or a separate login state to your agent.

Choose your first-task path

Managed task
External agent

Choose this path when you want BrowserPair to coordinate planning and execution.

Configure a Brain

Open Tools & settings → Brain + Reflex, add a supported Brain provider, and make it the account default. Reflex is optional.

Open Tasks

Describe the outcome you want in plain language.

Set task boundaries

Open Task settings, select the connected browser, and enter one or more allowed websites such as github.com, vercel.com.

Run and review

Start the task. BrowserPair will surface approvals, pauses, and the final durable state in the task history.

Managed task guide

See task settings, Skills, model overrides, limits, and pause behavior.

Choose this path when Claude, Codex, or another agent remains the Brain.

Create an agent key

Open Agent keys and create one key for this agent.

Scope the key

Choose the connected browser, allowed websites, capabilities, and approval preset.

Copy the token once

Store the full bp_live_… token in the agent’s secret manager. BrowserPair does not show it again.

Connect MCP or REST

Use the same key against the Remote MCP endpoint or REST API.

If an agent token is lost or exposed, rotate the key. The old token stops working immediately.

Remote MCP connection

Endpoint

https://mcp.browserpair.com

Authentication

Authorization: Bearer bp_live_…

The current MCP surface includes browser discovery, durable task creation/state, bounded Reflex subgoals, richer observations, agent responses, and cancellation.

Remote MCP reference

See every tool and the recommended external-agent loop.

First REST task

curl https://api.browserpair.com/v1/tasks \
  -H 'Authorization: Bearer bp_live_…' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: invoice-check-001' \
  -d '{
    "browserId": "brw_…",
    "goal": "Open the billing page and read the latest invoice status",
    "contract": {
      "version": 1,
      "domains": ["example.com"],
      "capabilities": ["read", "navigate", "click"],
      "confirmations": []
    }
  }'

One intended task should use one stable Idempotency-Key. Retrying the same request with that key returns the original task instead of creating duplicate work.

What a pause means

BrowserPair pauses rather than guessing when authority or certainty is missing.

A new website is required

The task cannot silently leave its effective website scope. A signed-in user may approve a bounded task-scoped domain grant when the reusable agent key permits it.

Sensitive data is redacted

Protected values stay hidden until the user grants the minimum matching sensitive-data category.

The next action needs confirmation

Approval presets and task-contract rules determine when BrowserPair asks before continuing.

The current observation is not enough

A Brain can request richer accessibility, DOM, screenshot, or combined context when account policy allows it.

An effect is uncertain

BrowserPair verifies or asks for resolution before retrying a side effect.

Brain + Reflex

Configure managed intelligence and provider routing.

Permissions

Understand the authority model before widening any scope.

Task semantics

Learn how tasks survive reconnects without blind replay.

Get Started

Use BrowserPair

Agent APIs

Concepts

BrowserPair Quickstart: Connect a Browser and Run a Task

1. Connect

2. Bound

3. Run

Connect your browser

Choose your first-task path

Managed task guide

Remote MCP connection

Endpoint

Authentication

Remote MCP reference

First REST task

What a pause means

Next

Brain + Reflex

Permissions

Task semantics

1. Connect

2. Bound

3. Run

​Connect your browser

​Choose your first-task path

Managed task guide

​Remote MCP connection

Endpoint

Authentication

Remote MCP reference

​First REST task

​What a pause means

​Next

Brain + Reflex

Permissions

Task semantics

Connect your browser

Choose your first-task path

Remote MCP connection

First REST task

What a pause means

Next