BrowserMan is built and maintained by a small team. Most issues we see are answered by the fixes below — if those don't help, email us and we'll usually reply within a day or two.
Try these first — they cover the great majority of reports we see.
Open the BrowserMan side panel and check three things:
https://browserman.run (or your self-hosted URL) — no trailing slash.If the badge still shows !, restart Chrome. The service worker can occasionally get into a stuck state that a fresh process clears.
The browser must be paired and the side panel must show connected (green) before any agent can drive it. Then:
bm_key_.BrowserMan groups its tabs into a Chrome tab group labeled 🤖 BrowserMan. Commands that need a tab will reuse a tab from that group, or open a new one inside it.
If a command landed in your personal tab, it usually means you sent the agent a command that explicitly targeted the active tab. Open a new tab inside the BrowserMan group and try again, or use a command that opens its own tab (for example navigate).
Open the side panel on that browser and click Restore. You'll see a list of names you previously used; pick the one that matches the device.
If the device is gone (e.g. wiped), revoke the entry from your dashboard — that immediately invalidates its key on the server.
From your dashboard you can:
For details on what we store and for how long, see the privacy policy.
Email support@browserman.run and we'll point you at the latest deployment guide. The Chrome extension itself is unchanged — it just talks to whichever server URL you configure in the side panel.
Please email support@browserman.run with details. We'll acknowledge within 48 hours.