From terminal to live feed in one command
bmc reads Chrome's already-decrypted traffic over the DevTools Protocol and streams it straight to the dashboard. No root CA, no proxy config, no certificate warnings — one command and you're live.
# 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# Windows (PowerShell) — same, self-updating:
irm https://cdp.busymate.net/install.ps1 | iex
bmc login
bmc create dev --browser chrome --startThe 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' — and it can shape that traffic too.
Zero trust setup — literally none
Because bmc taps the DevTools Protocol, the traffic is already decrypted. Nothing goes in a keychain, nothing throws a warning; capture starts the moment Chrome does.
Named browser devices
A background daemon manages independent Chrome profiles as named devices — start, stop and script each one from the terminal, the dashboard, or an MCP call. Your browsers become fleet members.
Mock and mutate, locally
The same sandboxed JS engine that powers the proxy runs against your real Chrome session: rewrite requests, synthesize responses, and watch every change land visibly in the feed.
BusyBro in your terminal
A native-scrollback REPL chat that knows this machine's devices. Ask it to create a browser, open a URL, run a check — actions are confirm-gated, and answers are grounded in your actual capture.
Never touch it again
The daemon self-updates when idle, reports its live build, and restarts on request from the dashboard or MCP. It's infrastructure that maintains itself.
Related: the real-time traffic dashboardMCP server for AI agents
Start capturing Chrome
Install bmc, sign in once, and your local Chrome traffic shows up live in the dashboard feed alongside every other source.