> ## Documentation Index
> Fetch the complete documentation index at: https://docs.browserpair.com/llms.txt
> Use this file to discover all available pages before exploring further.

# BrowserPair Quickstart: Connect a Browser and Run a Task

> Connect your Chrome profile and run a managed BrowserPair task or connect an external agent over MCP or REST.

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.

<CardGroup cols={3}>
  <Card title="1. Connect" icon="browser">
    Pair the Chrome profile you already use.
  </Card>

  <Card title="2. Bound" icon="shield">
    Define exactly which browser, websites, and actions are allowed.
  </Card>

  <Card title="3. Run" icon="play">
    Start from the dashboard, Remote MCP, or REST.
  </Card>
</CardGroup>

## Connect your browser

<Steps>
  <Step title="Install BrowserPair">
    Add the BrowserPair extension to the Chrome profile you want to use for agent work.
  </Step>

  <Step title="Start pairing">
    Open the extension and choose **Connect BrowserPair**.
  </Step>

  <Step title="Approve the browser">
    Complete the pairing approval in the BrowserPair app.
  </Step>

  <Step title="Confirm presence">
    Open **Browsers** in the dashboard. The profile should show **Online** while the extension is connected.
  </Step>
</Steps>

<Note>
  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.
</Note>

## Choose your first-task path

<Tabs>
  <Tab title="Managed task">
    Choose this path when you want BrowserPair to coordinate planning and execution.

    <Steps>
      <Step title="Configure a Brain">
        Open **Tools & settings → Brain + Reflex**, add a supported Brain provider, and make it the account default. Reflex is optional.
      </Step>

      <Step title="Open Tasks">
        Describe the outcome you want in plain language.
      </Step>

      <Step title="Set task boundaries">
        Open **Task settings**, select the connected browser, and enter one or more allowed websites such as `github.com, vercel.com`.
      </Step>

      <Step title="Run and review">
        Start the task. BrowserPair will surface approvals, pauses, and the final durable state in the task history.
      </Step>
    </Steps>

    <Card title="Managed task guide" icon="play" href="/managed-tasks">
      See task settings, Skills, model overrides, limits, and pause behavior.
    </Card>
  </Tab>

  <Tab title="External agent">
    Choose this path when Claude, Codex, or another agent remains the Brain.

    <Steps>
      <Step title="Create an agent key">
        Open **Agent keys** and create one key for this agent.
      </Step>

      <Step title="Scope the key">
        Choose the connected browser, allowed websites, capabilities, and approval preset.
      </Step>

      <Step title="Copy the token once">
        Store the full `bp_live_…` token in the agent's secret manager. BrowserPair does not show it again.
      </Step>

      <Step title="Connect MCP or REST">
        Use the same key against the Remote MCP endpoint or REST API.
      </Step>
    </Steps>

    <Warning>
      If an agent token is lost or exposed, rotate the key. The old token stops working immediately.
    </Warning>
  </Tab>
</Tabs>

## Remote MCP connection

<CardGroup cols={2}>
  <Card title="Endpoint" icon="plug">
    `https://mcp.browserpair.com`
  </Card>

  <Card title="Authentication" icon="key">
    `Authorization: Bearer bp_live_…`
  </Card>
</CardGroup>

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

<Card title="Remote MCP reference" icon="plug" href="/remote-mcp">
  See every tool and the recommended external-agent loop.
</Card>

## First REST task

```bash theme={null}
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": []
    }
  }'
```

<Tip>
  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.
</Tip>

## What a pause means

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

<AccordionGroup>
  <Accordion title="A new website is required" icon="globe">
    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.
  </Accordion>

  <Accordion title="Sensitive data is redacted" icon="key">
    Protected values stay hidden until the user grants the minimum matching sensitive-data category.
  </Accordion>

  <Accordion title="The next action needs confirmation" icon="shield">
    Approval presets and task-contract rules determine when BrowserPair asks before continuing.
  </Accordion>

  <Accordion title="The current observation is not enough" icon="eye">
    A Brain can request richer accessibility, DOM, screenshot, or combined context when account policy allows it.
  </Accordion>

  <Accordion title="An effect is uncertain" icon="arrows-rotate">
    BrowserPair verifies or asks for resolution before retrying a side effect.
  </Accordion>
</AccordionGroup>

## Next

<CardGroup cols={3}>
  <Card title="Brain + Reflex" icon="brain" href="/brain-reflex">
    Configure managed intelligence and provider routing.
  </Card>

  <Card title="Permissions" icon="shield" href="/permissions">
    Understand the authority model before widening any scope.
  </Card>

  <Card title="Task semantics" icon="arrows-rotate" href="/task-semantics">
    Learn how tasks survive reconnects without blind replay.
  </Card>
</CardGroup>