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

bash

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

# Capture this folder's Chrome → your Busymate feed:
bmc

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.

Its own Chrome per folder

bmc launches a dedicated Chrome (own port + profile + optional external proxy) for each working directory, so captures stay cleanly separated by project.

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