Browser profiles

Launch a known Chromium-family browser by id — bmc resolves its per-OS binary and applies sensible default flags, so you never have to remember a binary path or a flag list again.

What a browser profile is

A browser profile is a named recipe for launching a browser. Instead of hunting down the binary path for Brave on this OS and remembering which flags it needs, you name the profile and bmc does the rest:

• It resolves the binary for the browser you asked for, on whatever OS you're on.
• It applies that browser's default launch flags — the sensible set for capturing cleanly.
• It still lets you override either the binary or the flags when you need to.

Profiles come in two kinds: the four built-ins that ship with bmc (chrome, brave, edge, godbrowser), and custom profiles you author in the dashboard and that sync down to bmc.

Using it

Pass --browser <id> to bmc start or bmc create:

bmc start "My Device" --browser chrome     # capture here, launching Chrome
bmc create "Dev" --browser brave           # provision a named device on Brave

The chosen profile is persisted per device — once you start a device with --browser brave, it stays a Brave device until you change it; you don't re-pass the flag on every run.

Overrides

A profile is a starting point, not a cage:

# Use the godbrowser profile's flags, but point at a specific binary
bmc start "Dev" --browser godbrowser --chrome /path/to/GodBrowser
 
# Append your own flags after a bare -- (added on top of the profile's defaults)
bmc start "Dev" --browser chrome -- --lang=en-US --start-maximized

--chrome <path> overrides the resolved binary; everything after a bare -- is forwarded verbatim to the browser on top of the profile's defaults. See External proxy & custom Chrome for how binary resolution and pass-through flags work in general.

Inspecting profiles

bmc browser lists what's available; bmc browser <id> shows what a single profile knows:

bmc browser              # list every profile (built-in + your custom ones)
bmc browser brave        # inspect one: binary on this OS, default flags, full flag catalog

Inspecting a profile resolves it for your machine — so you see the actual binary path it would launch, the default flags it applies, and the full catalog of flags that profile documents.

The four built-ins

chrome

The default. Resolves Google Chrome (falling back to Chromium) and launches it with the baseline capture flags. This is what you get if you don't pass --browser at all.

brave

Resolves the Brave binary and applies Brave's defaults.

Heads up: Brave Shields can drop or block requests before they leave the browser — which means those requests never reach the network and so never appear in your capture. If a request you expect is missing on a Brave device, check Shields for that site before assuming a capture problem.

edge

Resolves Microsoft Edge. On Windows the binary lives under Program Files (x86), not Program Files — the profile knows this and resolves the right path automatically. Edge also runs extra Microsoft background services, so you'll see some additional first-party telemetry traffic in the feed compared with plain Chromium.

godbrowser

Resolves God Browser and exposes its large catalog of anti-fingerprint and automation flags. See the next section for the binary locations and the flag families.

God Browser reference

God Browser is a Chromium fork whose anti-fingerprint layer lives in the C++/V8 core — so its persona, fingerprint, and spoofing behaviour are present whenever Chrome is driven under CDP automation, not bolted on as an extension. The godbrowser profile surfaces the key flag families; the full, authoritative list is at godbrowser.io/integrate.

Flag families

Installing God Browser

Once installed, bmc start "Dev" --browser godbrowser launches it with the profile's defaults; add -- --bot-os=windows --bot-proxy-seed-country=US (or any other flags) to tune the persona. For the complete flag list and semantics, see godbrowser.io/integrate.

Custom profiles

Beyond the four built-ins, you can author your own profiles in the dashboard — handy for an internal browser build, a pinned Chromium version, or a house set of launch flags your team always uses.

Open Dashboard settings → CDP and add a profile with:

• a slug (the id you'll pass to --browser),
• a display name,
• per-OS binaries (the path to launch on macOS / Linux / Windows),
• default launch args, and
• an optional flag catalog (the documented flags bmc browser <slug> will show).

Custom profiles are stored in Supabase and sync down to bmc automatically — so bmc browser <slug> resolves them and bmc start "Dev" --browser <slug> launches them, exactly like a built-in.

How it resolves

Managing them over MCP

Custom profiles are also managed over MCP — list_browser_profile, get_browser_profile, upsert_browser_profile, and delete_browser_profile. Like the dashboard, those tools are RLS-gated: reads need devices:view and writes need devices:edit, so only people who can manage devices can change which browsers a device may launch.

Next

• External proxy & custom Chrome — route through an upstream proxy and override the binary or flags.
• Remote control — drive a captured browser from the dashboard, MCP, or BusyBro.
• Command reference — every bmc command and flag.