Overview

The CDP Connector (bmc) captures a Chrome instance's already-decrypted traffic over the Chrome DevTools Protocol — no proxy, no certificate, no MITM.

What it is

bmc is a small command-line tool you run on your own machine. Point it at a folder, and it launches (or attaches to) a Chrome instance and streams that browser's network traffic straight into your Busymate dashboard — every request and response, decrypted, in real time.

Because it reads traffic through Chrome's own DevTools Protocol, there's nothing to intercept and nothing to trust:

• No proxy to configure on the device.
• No Root CA to generate or install.
• No MITM — Chrome has already decrypted the TLS itself, and bmc just observes it.

That's the whole point: zero trust setup. You install one command, sign in once, and start capturing. Compared with the web proxy (which mints a CA and intercepts TLS) or iOS (which runs a packet tunnel), the CDP path is the lightest way to get a browser's traffic into Busymate.

How it fits together

Chrome  ──DevTools Protocol──▶  bmc  ──▶  Busymate (ingest)  ──▶  Dashboard feed

Each captured request becomes a traffic entry tagged with source: "cdp" and a Chrome badge, and lands in your dashboard feed right next to traffic from every other device.

A folder is a device. Run bmc in ~/work/app-a and you get one device; run it in ~/work/app-b and you get another — each with its own Chrome instance, on its own debug port. The dashboard treats them like any other paired device: rename them, set per-device capture rules, set breakpoints, route them through an upstream proxy, and even drive them remotely.

Why you'd reach for it

• Capturing a web app or site you're building, without touching your everyday browser.
• Debugging a backend through the browser — see exactly what the front end sends and receives.
• Running headless / CI captures (sign in with environment variables, no browser prompt).
• Many parallel captures on one machine — each folder runs an independent Chrome.

Next steps

• Install & sign in — one command, then bmc login.
• Capture a Chrome — run bmc in a folder and watch the feed fill.
• Named devices & the daemon — provision named devices that survive reboots.
• Command reference — every command and flag.

Tip: Want the internals — the CDP translation layer, the ingest path, the control plane? See CDP Connector architecture.