security. Bind the CDP port to 127.0.0.1 as the README does; an exposed CDP port lets anyone drive the Browser.
Who it is forA team paying for memory hungry headless Chrome fleets.
The problemHeadless Chrome uses gigabytes of memory per batch of pages.
The outcomeYour Puppeteer script running against Lightpanda on port 9222.
What you need first
- Linux or macOS (x86_64 or aarch64); Windows only through WSL2; Linux binaries need glibc
- Install with `brew install lightpanda-io/browser/lightpanda`, a nightly binary, Nix or `docker run -d --name lightpanda -p 127.0.0.1:9222:9222 lightpanda/browser:latest`
- puppeteer-core or Playwright if you connect your own scripts over CDP
Steps
- Install Lightpanda, or run it in Docker with
docker run -d --name lightpanda -p 127.0.0.1:9222:9222 lightpanda/browser:latest - Start the server with
./lightpanda serve --obey-robots --log-format pretty --log-level info --host 127.0.0.1 --port 9222 - In your script, call puppeteer.connect with browserWSEndpoint ws://127.0.0.1:9222 instead of launching Chrome
- Use
--protocol webdriverif your client needs WebDriver BiDi
Prompt for your agent
With lightpanda-io/browser, start the CDP server on 127.0.0.1:9222 and change <my Puppeteer script> to connect with browserWSEndpoint, then compare its run time against Chrome.
Caveat. Lightpanda implements a growing subset of web APIs, so test pages that rely on unusual Browser features.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for lightpanda-io/browser and "Run existing Puppeteer scripts on a lighter Browser"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer