Update & remove

Self-update bmc and remove devices you no longer need.

Keep bmc current, check its state, list your devices, and remove the ones you no longer need.

Update

bash
bmc update

bmc checks the dashboard for the latest published build. If a newer one is out, it re-runs the same one-line installer you used originally (the bash installer on macOS/Linux, the PowerShell one on Windows) to update in place. After updating, it re-stamps the build for every device configured on this machine, so the dashboard immediately shows the new version — no need to wait for the next capture.

If you're already current, it still re-stamps the build, so the dashboard stays accurate.

[bmc] updating build 41 → 42…
[bmc] dashboard version updated to build 42 for 3 devices on this machine.

A new build also surfaces a one-line banner when you run bmc start, so you'll know an update is available even if you don't check.

Note: Updates are served live by the dashboard, so bmc update always pulls the latest published build for your OS.

Status

bash
bmc status

Shows your sign-in state, this directory's device, the Chrome endpoint, and the effective capture settings — a quick way to confirm a folder is set up and signed in.

List your devices

bash
bmc list          # devices configured on THIS machine
bmc ls            # same — short alias
bmc ls --all      # every device you own, across all machines (+ live status/version)
bmc ls --json     # machine-readable output

By default, bmc list shows only the devices configured on this machine — name, folder, CDP host:port, and Chrome binary — with no network call. Add --all (-a) to pull every device you own from the dashboard, enriched with kind, version/build, and whether each is online:

bmc — 3 devices (all machines) · you@example.com
 
   NAME       KIND          VER       PORT   SEEN       PATH        UUID
  ─────────────────────────────────────────────────────────────────────
  ● App A     cdp·Chrome    v1.0(42)  :9222  12s ago    ~/work/a    8f3c…
  ○ App B     cdp·Chrome    v1.0(42)  :9223  off 2h ago ~/work/b    1a7e…
 
  ● online  ○ offline   ·   PORT/PATH are local to this machine (— = paired elsewhere)

bmc ps lists your named daemon devices specifically, with their running state.

Remove a device

bash
bmc remove           # remove THIS folder's device (confirm-gated)
bmc remove "Staging" # remove a named daemon device
bmc remove --yes     # skip the confirmation prompt

bmc remove deletes the device server-side — the device row and all its captured entries — then clears the local ./.bmc.json (for a folder device) or its registry entry (for a named device). For a folder device it confirms first, unless you pass --yes (-y) or run non-interactively.

Heads up: Removal deletes the device's captured data in the dashboard too. It can't be undone.

You can also remove a device from the dashboard under Devices — a running bmc notices the unpair, clears its local .bmc.json, and exits cleanly.

Sign out

bash
bmc logout

Clears the saved session at ~/.busymate-cdp/auth.json. Your per-folder device files (.bmc.json) are left untouched — run bmc login to sign in again.

Next

Command referenceOverview