Repository navigation
v0.4.0
Adds the optional CDP response-body tier (phase b of the CDP work), behind a deny-by-default origin allowlist. Also covers the trusted-input tier from the previous cycle, which had not yet been released.
Install
npm install -g chrome-browser-control
npx -y chrome-browser-control setupPublishing is manual from a maintainer machine. There are no CI publish credentials.
New: response-body capture, opt-in and off by default
Three tools, usable only after cdp_attach:
cdp_network_watch— enables the Network domain and keeps an in-memory index of metadata rows only. No body is read or stored.cdp_network_requests— returns that index.cdp_response_body— reads one body, for one request, on demand.
This narrows a previously blanket guarantee, deliberately and with controls attached:
- Deny by default. Body capture uses a second allowlist in the extension popup, separate from Allowed Origins. An empty list means no body is readable.
*is not a valid entry — the wildcard that works for page actions does not work here. - A restricted-category denylist wins unconditionally, even over an origin you listed explicitly.
- Nothing is buffered. Bodies are fetched one request at a time, never held.
- Binary bodies and oversize bodies are refused, never truncated.
- Best-effort masking of obvious token-shaped fields — not a guarantee. Treat any response body as if it contains credentials.
- Response headers,
Set-Cookie, and request post data are never exposed, at any tier. - Every successful read is recorded to an append-only metadata log at
~/.chrome-browser-control/, mode0600. Body content is never written there.cbctl statussurfaces the count.
The CDP tier may still send only an enumerated list of protocol methods, enforced in code. Fetch, Network.setRequestInterception, Network.continueInterceptedRequest, and Runtime.evaluate remain forbidden: this project reads traffic and never modifies it.
Also in this release
Trusted CDP input — cdp_attach / cdp_detach, with click, type, keypress and click_at routed through real input events while attached.
Known limitations
Response-body index invalidation across navigation is not unconditional in one narrow case. See the follow-up issue for the exact preconditions. Nothing there bypasses the body-capture allowlist.
Guidance
This is an opt-in debugging tier for deliberate, task-scoped use on origins you typed in yourself. It is not safe to switch on and leave on. Prompt injection is not mitigated by it, and anything read enters your session transcript permanently.