A headless browser that renders pixels only under duress

What it does

Moli is a standalone headless browser kernel written in Rust for AI agents and automation pipelines. It fetches pages, executes JavaScript, and speaks standard protocols like CDP and WebDriver, but it does not wrap Chromium. The native DOM and computed styles serve as the single source of truth, keeping the runtime lightweight until visual output is strictly necessary.

The interesting bit

Its on-demand rendering model treats layout and paint as expensive, optional operations. For structure-only tasks—extracting HTML, Markdown, or semantic trees—Moli skips geometry and rendering entirely. It only builds a temporary working layout tree, calculates boxes, or produces a software frame when a screenshot, PDF, or coordinate input is requested, then discards that transient state.

Key highlights

• Built from discrete Rust components rather than wrapping an existing browser binary: rusty_v8 for JavaScript, Servo/Stylo for CSS, Taffy and Parley for layout, and Vello CPU for software rendering.
• Exposes CDP, WebDriver Classic, and WebDriver BiDi from a single binary, so clients like Playwright connect directly without a separate ChromeDriver.
• README benchmarks report a median RSS of 73 MiB versus 773 MiB for Chrome Headless across a 192-site crawl, with comparable success rates and median load times.
• On an agent workload, it reportedly reaches CDP ready in roughly 35 ms and peaks under 103 MiB, against Chromium’s 169 ms and 349 MiB.
• Unsupported protocol paths return explicit errors instead of silent failures.

Caveats

• The project deliberately omits a GPU compositor, persistent window, and retained multi-frame paint architecture, so it is not a universal drop-in replacement for every Chrome Headless workflow.
• High-fidelity Canvas, WebGL, and media playback are explicitly out of scope, and some Chrome screenshot or print modes remain unimplemented.

Verdict

Best suited for developers running crawls, retrieval pipelines, or browser-use agents where DOM structure and low memory matter more than visual fidelity. If your workload requires GPU-accelerated rendering, complex WebGL, or perfect Chrome parity, stick with Chromium.