CLI · bmc

Capture your local Chrome, decrypted, in one line

Busymate Chrome (bmc) streams already-decrypted Chrome DevTools Protocol traffic straight into your feed — no MITM, no root CA, no proxy setup.

Read the docs

bmc — zsh

$ bmc login
✓ signed in as you@example.com
$ bmc start
▸ launching Chrome (throwaway profile)
 connected · streaming to dashboard
GETapi.example.com/v1/feed200
POSTevents.example.com/track200
GETcdn.example.com/app.js200

Install & capture · macOS / Linux

bash

# macOS / Linux (self-updates from the dashboard):
curl -fsSL https://cdp.busymate.net/install.sh | bash

# Sign in once, create a browser, and capture it → your Busymate feed:
bmc login
bmc create dev --browser chrome --start

Install & capture · Windows

powershell

# Windows (PowerShell) — same, self-updating:
irm https://cdp.busymate.net/install.ps1 | iex

# Sign in once, create a browser, and capture it → your Busymate feed:
bmc login
bmc create dev --browser chrome --start

Why bmc

The simplest capture source

When you're debugging a web app on your own machine, bmc is the fastest path from 'open Chrome' to 'inspect every request in Busymate'.

No MITM, no CA, no proxy

bmc reads traffic Chrome has already decrypted via the DevTools Protocol — nothing to trust, no certificate to install, no proxy to configure. Just point it at a Chrome and go.

Real requests, full detail

Every request/response — method, URL, status, headers, query, and body — streams into the same dashboard feed as your iOS and proxy captures.

A daemon that manages your browsers

bmc runs a background supervisor that manages your browsers as named devices — each with its own port, profile, and optional external proxy. Start, stop, and drive them from the live bmc console, the dashboard, or MCP.

Start capturing Chrome

Install bmc, sign in once, and your local Chrome traffic shows up live in the dashboard feed alongside every other source.

Read the docs Open the dashboard