From terminal to live feed
Un comando. El tráfico de Chrome aterriza en el mismo feed en vivo — sin certificados que instalar.
# 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
El camino más rápido de «abrir Chrome» a «inspeccionar cada petición» — y también puede moldear ese tráfico.
Cero configuración de confianza — literalmente ninguna
Como bmc lee el DevTools Protocol, el tráfico ya está descifrado. Nada entra en un llavero, nada lanza avisos; la captura empieza en cuanto arranca Chrome.
Dispositivos de navegador con nombre
Un demonio en segundo plano gestiona perfiles de Chrome independientes como dispositivos con nombre — arranca, detén y programa cada uno desde la terminal, el panel o una llamada MCP. Tus navegadores se vuelven parte de la flota.
Simula y muta, en local
El mismo motor JS aislado que impulsa el proxy corre contra tu sesión real de Chrome: reescribe peticiones, sintetiza respuestas y mira cada cambio aterrizar visible en el feed.
BusyBro en tu terminal
Un chat REPL con scrollback nativo que conoce los dispositivos de esta máquina. Pídele crear un navegador, abrir una URL, correr una comprobación — las acciones piden confirmación y las respuestas se basan en tu captura real.
No vuelvas a tocarlo
El demonio se actualiza solo cuando está inactivo, informa su build en vivo y se reinicia a petición desde el panel o MCP. Es infraestructura que se mantiene sola.
Reads Chrome traffic
bmc attaches to Chrome over the DevTools Protocol — the same wire DevTools itself uses — so it sees requests exactly as the browser does: already decrypted.
- 01
Its own Chrome, per folder
bmc start launches a dedicated Chrome with its own profile and its own debug port for the current directory. Each folder is an independent device — run it in two folders and you get two fully separate browsers.
- 02
Attach over the DevTools Protocol
It connects to Chrome's debug port over a WebSocket, auto-attaches to every tab, and enables the Network domain — the same wire Chrome DevTools itself uses. No extension, no proxy in the path, nothing injected into pages.
- 03
Events become entries
Request, response and timing events are correlated into the same entry shape every Busymate source uses, with headers and bodies (up to 1 MB per body) pulled straight from the browser — after Chrome already decrypted them.
- 04
Batched into one feed
Entries are batched and posted to the ingest API about once a second. The folder pairs as a real Busymate device, so its traffic lands in the same dashboard, the same filters, the same MCP tools and the same HAR export as every phone.
Capture without
TLS terminates inside Chrome, and bmc reads on the browser's side of it. There is no man-in-the-middle to trust — so there is nothing to install, and nothing for pinning to detect.
A proxy debugger decrypts HTTPS by re-signing it with its own certificate authority — which means installing that CA, trusting it in a keychain, and losing the apps that pin their certificates. bmc skips the whole problem: the DevTools Protocol hands over each request after Chrome has already decrypted it.
| What it takes | bmc (CDP) | Proxy (MITM) | iOS / Android app |
|---|---|---|---|
| Root CA to install | None | Yes — trust the proxy CA | Yes — on-device CA, decrypting only domains you opt in |
| Network setup | None | Point each client at the proxy | None — an on-device VPN tunnel |
| Pinned certificates | Unaffected — nothing sits in the TLS path | Pinned apps refuse the proxy CA | Pinned apps stay encrypted (metadata still visible) |
| What it sees | The Chrome it launches — every tab | Any app or script you point at it | Every app on the phone |
| Best for | Web apps, SPAs, agent-driven browsing | Backends, scripts, browsers on other machines | Mobile apps, in the field |
Each path is first-class: the proxy and the phone apps exist precisely for the traffic CDP can't see. Use bmc for browsers, the proxy for anything you can point at it, and the apps for whole-phone capture.
Drive the browser.
Every bmc browser is remote-controllable over MCP — an AI agent or a script can open pages, read them and act, while capture records every request the session makes. That combination is the point.
Drive and read the page
- browser_open
- Navigate the browser to a URL.
- browser_targets
- List the open tabs and pick the one to drive.
- browser_snapshot
- A compact accessibility-tree snapshot — the page as structured text, built for agents.
- browser_screenshot
- A PNG of the active page.
- browser_eval
- Run JavaScript in the page. Placeholder variables are resolved server-side from the device's env, so an agent can fill a login form without ever seeing the password.
- browser_cdp
- Raw DevTools Protocol access for everything else — owner-gated.
Browser profiles
Built-in Chrome, Brave and Edge profiles plus custom ones authored once in the dashboard — per-OS binaries, default flags and a flag catalog every machine's bmc resolves the same way.
- list_browser_profiles
- get_browser_profile
- upsert_browser_profile
- delete_browser_profile
The daemon, remotely
Live build, uptime and logs without SSH; list every named browser on a machine; restart or hot-update the daemon while running captures keep capturing. One switch arms or disarms it all, per device.
- get_cdp_daemon_status
- get_cdp_logs
- list_cdp_instances
- restart_cdp_daemon
- update_cdp_daemon
- set_device_cdp_control
Remote control is opt-in per device and permission-gated; capture keeps flowing either way.
Una identidad de dispositivo coherente,
GodBrowser es un Chromium anti-fingerprint que da al navegador una identidad de dispositivo coherente y con aspecto real. Es un perfil de navegador integrado en bmc, así que un agente puede ejecutar una persona y capturar su tráfico en el mismo feed en vivo que tus teléfonos.
Selecciona GodBrowser con un solo flag y bmc lo controla mediante el mismo DevTools Protocol que cualquier otro dispositivo de navegador: inspecciona cada solicitud que hace la persona —ya descifrada, sin CA raíz, sin proxy— y las transmite a tu feed de Busymate. GodBrowser presenta a bmc como su compañero de inspección de solicitudes para exactamente este emparejamiento.
Una identidad, toda de una pieza
El user-agent, la pantalla, WebGL, canvas y audio, el locale y la zona horaria concuerdan con la persona, y TLS/JA4, UA-CH y los códecs se alinean con el dispositivo declarado antes de que se ejecute una línea de JavaScript. Como lo plantea GodBrowser: un dispositivo real, no uno disfrazado.
Semillas deterministas
El flag --bot-profile deriva una identidad de dispositivo completa a partir de una cadena semilla. Cambia la semilla, cambia el dispositivo: repetible y reproducible, así que una persona se reproduce exactamente igual.
Personas por plataforma y navegador
Windows, macOS, Linux, iOS y Android combinados con Chrome, Safari, Firefox, Samsung Internet y Edge, seleccionados con --bot-os y --bot-browser. Su base es un Chromium 151 parcheado.
Clúster, API y MCP
GodBrowser se ejecuta en tu propio clúster de nodos, controlado desde código, su API o un cliente de IA, y ofrece su propio servidor MCP remoto. Los proxies se asignan por perfil de forma determinista; las sesiones se sincronizan entre máquinas mediante Redis.
# GodBrowser is a built-in bmc browser profile — pick it per device:
bmc create ios-persona --browser godbrowser -- \
--bot-os=ios --bot-browser=safari --bot-profile=seed-42 --startGodBrowser es uno de los perfiles integrados de bmc, junto a Chrome, Brave y Edge: seleccionarlo con --browser godbrowser es toda la configuración. bmc resuelve el binario, expone sus flags de persona, empareja el dispositivo como un “God Browser” distinto y etiqueta su tráfico capturado como gdp para que destaque en el feed. No se inyecta nada en GodBrowser: bmc lo controla mediante el DevTools Protocol, y su capa anti-fingerprint vive en el núcleo del navegador, así que permanece intacta bajo automatización. Ambas herramientas son nativas de MCP: el servidor MCP remoto de GodBrowser y el de Busymate hacen que un mismo agente pueda controlar personas y leer su tráfico en una sola sesión, cada una tras su propio token basado en consentimiento.
One tool,
Agent-driven QA
An assistant opens your staging site, walks the flow and screenshots what it sees — while the network feed shows exactly what broke, with full request and response bodies.
Debug a SPA
Watch XHR and fetch calls stream live with headers, bodies and timings while you click through the app. The history survives a reload — no DevTools-tab archaeology.
Capture an OAuth flow
Redirect chains, tokens and callbacks recorded end to end — including on providers whose pinned certificates a proxy can't open.
Work a signed-in page
The folder's Chrome profile keeps its session between runs; snapshot and eval read the page while capture documents every request behind it.
The sceptical
Does bmc need a certificate or a proxy?
No. It attaches to Chrome over the DevTools Protocol and reads traffic after Chrome has decrypted it. There is no root CA to install, no keychain trust prompt, and no proxy settings to change.
Does it work with certificate pinning and HSTS?
Yes. Pinning defends the TLS connection between Chrome and the server — bmc never touches that connection; it reads inside the browser. HSTS, corporate device policy and managed keychains are equally unaffected.
Does it modify pages or the sites I visit?
Capture injects nothing — bmc listens to Chrome's own network events. It also launches its own Chrome with its own profile, so your everyday browser is never touched.
Can it run headless or in CI?
Yes. Anything after -- goes straight to Chrome (for example --headless=new), and CDP_USER_JWT or CDP_PAIR_EMAIL and CDP_PAIR_PASSWORD sign in without opening a browser.
Which browsers does it support?
Chromium-family browsers: built-in Chrome, Brave, Edge and Chromium profiles, plus custom profiles you author in the dashboard. Anything that speaks the DevTools Protocol.
What about traffic outside the browser?
bmc only sees the Chrome it is attached to. For backends and scripts use the Busymate proxy; for whole-phone capture use the iOS or Android app — everything lands in the same feed.
Start capturing
Instala bmc, inicia sesión una vez y el tráfico de Chrome aterriza en el mismo feed en vivo.