purecdp

Pure-Python (stdlib-only) library for the Chrome DevTools Protocol, targeting Python 3.14+.

Three things, layered:

1. purecdp.protocol — low-level typed bindings, generated from the official devtools-protocol JSON specs.
2. purecdp core — sans-I/O protocol engine + asyncio transports (websocket / pipe) + browser launcher.
3. purecdp.testing — opinionated helpers for driving a browser in tests, incl. a pytest plugin.

See Examples.md for task-grouped recipes (basics, testing, stealth, LLM agents, frames).

Quickstart

import asyncio
import purecdp
from purecdp.protocol import page, runtime

async def main():
    async with await purecdp.launch() as browser:   # finds Chromium/Chrome/Brave
        session = await browser.new_session()          # create target + attach

        await session.execute(page.enable())
        waiter = asyncio.create_task(session.wait_for(page.LoadEventFired))
        await asyncio.sleep(0)  # subscribe before triggering
        await session.execute(page.navigate(url="https://example.com"))
        await waiter

        result, _ = await session.execute(
            runtime.evaluate(expression="document.title", return_by_value=True))
        print(result.value)

asyncio.run(main())

purecdp.launch(pipe=True) uses --remote-debugging-pipe instead of a websocket. browser.new_page() is the one-call convenience — a new tab as a ready testing.Page. purecdp.connect("http://127.0.0.1:9222") (or host=/port=, or a ws:// endpoint) attaches to a browser someone else started — notably a browser a human just logged into (password, MFA), so an agent can inherit the authenticated session while the credentials never touch the automation; a new tab shares the profile's cookies, so it's signed in from birth. browser.new_context() gives an isolated cookies/storage context (cheap per-test isolation); connection.set_auto_attach() auto-attaches popups/workers/OOPIFs, resuming paused targets automatically.

Writing tests with purecdp

The stdlib way (purecdp.testing.CDPTestCase — fresh browser, isolated context, and a Page per test):

from purecdp.testing import CDPTestCase, JSError

class MyAppTests(CDPTestCase):
    async def test_stubbed_api(self):
        async def api(request):
            await request.fulfill(body='{"items": []}',
                                  content_type="application/json")
        await self.page.route("*/api/*", api)
        await self.page.goto("https://myapp.example/", wait="idle")
        await self.page.wait_for("#empty-state")
        assert not self.page.js_errors

Page gives you goto (load/idle waits), evaluate (promises awaited, JSError raised; values pass as arguments — evaluate("(a, b) => a + b", x, y) — never interpolated into JS source), wait_for(selector, **conditions) (present / visible=False gone-or-hidden / count=0 absent — the should() vocabulary), wait_for_function, click, query/query_all (held elements, text-filtered, stale-copy-proof), screenshot, always-on page.console / page.js_errors capture, and page.route() request stubbing/rewriting/aborting. For traffic-level assertions there's page.record() (full request/response exchanges — the wire headers, Cookie / Origin / Set-Cookie included, plus bodies, and parse_sse() for streamed ones) and page.expect_download() (capture a download's bytes without touching disk); arm recorder.expect() before a click and await .value for the response it triggers (json=True skips interleaved non-JSON bodies), and recorder.save_har() writes the whole capture as a HAR any devtools opens. Sensitive flows keep their privacy: record(bodies=False) captures metadata only, and record(redact=...) makes matching exchanges fully private (no bodies, credential headers masked) — the secret never enters the process. And when a test fails, its pages are dumped as diagnostic artifacts — screenshot, HTML, console, recorded traffic, traceback — under purecdp-artifacts/<test id>/ before the browser closes; green tests write nothing.

For SPA-proof tests there are lazy locators: page.live(selector) and get_by_test_id / get_by_text / get_by_role / get_by_label hold the query, not a node — every action re-resolves against the current DOM (a React remount can't leave you a stale handle), auto-waits for actionability, and one .should(...) gives polling assertions:

await page.get_by_test_id("chat-input").fill("hello")
await page.get_by_role("button", name="Send").click()
await page.live(".msg", containing="hello").should(visible=True, count=1)
await page.live(".spinner").should(count=0)          # waits until it's gone

Prefer pytest? The optional plugin (auto-registered when installed, or -p purecdp.testing.pytest_plugin) provides a session-scoped cdp_browser and per-test cdp_page, and runs async def tests itself — no pytest-asyncio required:

async def test_title(cdp_page):
    await cdp_page.goto("data:text/html,<title>hi</title>")
    assert await cdp_page.title() == "hi"

Low-observability / stealth

For automation that shouldn't advertise itself, purecdp layers three opt-in pieces (reduces common detection signals — not a promise of undetectability; CreepJS-class and TLS/HTTP2 fingerprints still identify automation):

import purecdp
from purecdp.testing import Page, apply_stealth

async with await purecdp.launch(stealth=True) as browser:   # AutomationControlled off, headless=new
    session = await browser.new_session()
    page = await Page.create(session, capture=False, track_network=False)  # no Runtime.enable leak
    await apply_stealth(page)                                # fingerprint init-scripts, before goto
    await page.goto("https://example.com")

apply_stealth(page, evasions=[...]) selects a subset; keyword overrides (webgl_vendor, webgl_renderer, languages, vendor, hardware_concurrency) tune the spoofed values.

For behavioral realism (the more durable signal — how input moves, all over trusted Input events):

el = await page.query("#submit")
await el.human_click()             # curved, eased path to a near-center point
await page.human_type("hello@example.com")   # per-key events, human cadence
await page.human_scroll(1200)      # eased wheel steps, not one jump

Since purecdp drives a real browser, its TLS/HTTP2 (JA3/JA4) fingerprint is already authentically Chrome's — no spoofing needed, unlike browserless HTTP scrapers.

Driving with an LLM (agent surface)

page.snapshot() returns a compact, ref-tagged view of the page from the accessibility tree — small and stable enough to hand an LLM, instead of raw HTML or screenshots. Each control gets a session ref (e1, e2, …); password fields are masked.

snap = await page.snapshot()
print(snap)
# - RootWebArea "Login"
#   - textbox "Email" [e1]
#   - textbox "Password" = "••••••" [e2]
#   - button "Sign in" [e3]

await page.act("e1", "fill", text="me@example.com")   # fill/type/select/click/…
await page.act("e3", "click")
el = await page.element_for_ref("e1")                  # escape hatch: full Element API

An optional MCP server exposes this to any Model Context Protocol host — no extra dependency, stdlib JSON-RPC over stdio:

python -m purecdp.mcp            # navigate/snapshot/act + network/wait/seed tools
python -m purecdp.mcp --stealth  # low-observability launch
python -m purecdp.mcp --allow-eval   # also expose the JS evaluate tool
python -m purecdp.mcp --allow-mock   # also expose the response-stubbing tool

Beyond driving the DOM, the server exposes the recorder so an agent can assert on the wire: after act, the returned cursor feeds requests(since=cursor) to see what the click fired, then request(id, select="a.b") reads just that part of the response body (semantic projection, so a huge body doesn't flood the agent's context). act targets an element by snapshot ref or by description (by=text/role/testid/label); snapshot returns the ref-tagged outline or (format="json") a flat list of {ref, role, name} rows, and (scope="dialog") narrows to the open modal's controls; screenshot returns a PNG image block for visual state; plus wait (until visible/hidden/ count/text), seed_storage / set_cookie (plant an auth session before navigating), record (narrow capture), and mock (stub an endpoint, opt-in).

Layout

spec/               vendored protocol JSON + PIN (source commit)
src/purecdp/            the library (src layout)
src/purecdp/_generator/ code generator (dev tool, reads spec/, writes src/purecdp/protocol/)
src/purecdp/protocol/   GENERATED bindings — do not edit by hand
tests/              tests and test utilities

Regenerating the bindings

python -m purecdp._generator          # uses spec/ and src/purecdp/protocol/ defaults

Update spec/*.json + spec/PIN from a devtools-protocol checkout first when moving the pin.

Running tests

Stdlib only — no test dependencies:

python -m unittest              # discovery from repo root
python tests/test_protocol.py   # single file works too

python -m pytest also works (nicer output, subtest counts) but is never required.