BrowserPilot Support

We're here to help.

If BrowserPilot isn't working right now, this page will get you unstuck in minutes.

60-Second Triage

Bridge Won't Start

Commands to launch and verify the local server connection.

Extension Not Connecting

Steps to resume through the BrowserPilot install path and support recovery flow.

Activation Failed

How to check your entitlement status and re-setup.

Detailed Troubleshooting

1. Bridge Won't Start

The bridge connects your MCP client and the browser. If it won't start:

  1. Open your terminal
  2. Run the runtime status command:
browserpilot status

What you should see: an active device session and the local BrowserPilot bridge endpoint on port 9225.

If that didn't work: Re-run the BrowserPilot setup command from your account panel to reinstall the bridge and refresh local runtime configuration, then run browserpilot status to confirm the restored runtime.

2. Extension Not Connecting

If the extension is missing, blocked, or no longer responding, recover it through BrowserPilot's owned install and support path instead of Chrome's raw extension-management UI.

  1. Open Google Chrome
  2. Open the BrowserPilot install page and use the current install flow to continue setup or repair delivery
  3. Open BrowserPilot from your Chrome toolbar after the install flow finishes
  4. If claim delivery, activation, or runtime repair is still blocked, email [email protected] with your account email, order/access reference ID, and OS

What you should see: BrowserPilot returns through its own install/support flow, then the extension popup displays a green "Active" status and reconnects to the WS/SSE bridge.

If that didn't work: Confirm your Claude Desktop or VS Code MCP configuration still points to http://127.0.0.1:9225/sse, then continue through /install or support instead of manual extension-page recovery.

3. Activation Failed

Sometimes your local session token expires or becomes invalid.

  1. Check your current status:
browserpilot status
  1. If it says "Expired" or "Invalid", clear the local session and re-run setup from your account panel:
browserpilot logout
browserpilot setup

What you should see: A browser window will open, activate your license, and the terminal will output "Setup complete. Entitlement valid."

Frequently Asked Questions

Pricing & Catalog Vocabulary

Your invoice may show different plan names than the current website. This is normal — your subscription is unaffected. Email us if anything looks off.

How do I check if the bridge is running?

Run browserpilot status in your terminal or navigate to http://127.0.0.1:9225/ping in your browser. You should see an active device session and the local bridge endpoint, and the ping route should return an "ok" status.

What MCP URL do I use?

In your MCP client configuration (e.g. VS Code or Claude Desktop), the server command should point to the SSE endpoint: http://127.0.0.1:9225/sse.

How do I update BrowserPilot?

Use the BrowserPilot setup command shown in your account panel to pull the latest runtime helper, then run browserpilot status to confirm the refreshed local runtime. The Chrome extension self-updates via the Chrome Web Store.

Does BrowserPilot work with Chrome profiles?

Yes. The extension runs in the profile where it's installed. Ensure you are targeting the correct window.

Why does Chrome show "debugging this tab" bar?

This is a Chrome security feature indicating that an extension is controlling the page via the Chrome DevTools Protocol. It ensures you know when automation is active.

How do I use multiple tabs?

You can tell your agent to use the mcp_browserpilot_browserpilot_list_tabs tool to see available tabs, and then direct commands at specific tabs.

How do I revoke my device session?

Run browserpilot logout. This will destroy your local token and revoke it on the server.

What operating systems does BrowserPilot support?

BrowserPilot supports macOS and Windows via Node.js and Google Chrome. Linux support is not yet available.

Escalation Path

Still stuck? We'll get this sorted out.

Diagnostics Bundle

To speed up your ticket, please generate a diagnostics bundle and include it in your email:

browserpilot status --verbose

Please include in your email:

  1. Your Operating System (e.g., Windows 11, macOS Sonoma)
  2. Your Node.js and Chrome versions
  3. The exact error message you are seeing
  4. The output from the verify and status commands
  5. Screenshots of the issue (if applicable)
← Back to BrowserPilot