One browser. Your agent drives, you take the wheel.

• Mint a one-time viewer link for any supervised session over REST, either SDK or MCP. Deliver it however your product already reaches people: your queue, chat or email.
• Mint a fresh link for each person who steps in. A used link can’t be opened again.
• Give each agent its own API key. The viewer shows the session and the key that started it, with a running list of the agent’s actions.
• Your account lists every supervised session with its status and who has control, and you can open or stop any of them.
• One rate for agent and operator minutes, so a handoff never changes the price.

The link opens Rove’s viewer in the operator’s browser.

{
  "mcpServers": {
    "rove": { "command": "npx", "args": ["-y", "@roveapi/mcp"] }
  }
}

import { BrowserClient } from '@roveapi/browser'

const rove = new BrowserClient({ apiKey: process.env.ROVE_API_KEY! })

// Your agent drives this session; a person can take control at any time.
const session = await rove.session({ supervised: true })
await session.navigate('https://dashboard.vendor.example/invoices')

// A one-time link for the person supervising.
const { viewerUrl } = await rove.createViewerGrant(session.id)
console.log(`Watch or take control: ${viewerUrl}`)

import os

from roveapi import BrowserClient

rove = BrowserClient(api_key=os.environ["ROVE_API_KEY"])
session = rove.session(supervised=True)
session.navigate("https://dashboard.vendor.example/invoices")
grant = rove.create_viewer_grant(session.id)
print("Watch or take control:", grant["viewer_url"])
rove.close()

MCP setupSupervised sessionsAPI reference

• Agent driving · filling in a supplier onboarding formYour turn · sign the tax form
• Agent driving · checking out a restock orderYour turn · enter the bank’s 3-D Secure code
• Agent driving · signing in to the vendor portalYour turn · type the code from your authenticator app
• Agent driving · drafting replies in the support inboxYour turn · read them before they send

Passwords and codes go from your keyboard into the page. They never pass through your agent’s chat.

• One driver at a time. While you’re in control, the agent can’t click or type.
• Viewer links work once, from the site they were made for.
• Every supervised session runs in its own browser worker.
• Sign-ins stay with your browser profile, so you log in once, not every session.
• After you hand back, the agent re-reads the page before it acts.