Your existing Puppeteer scripts, running against a browser that understands what you meant when the selector breaks.

LumaBrowser’s puppeteer-driver extension is a standards-compliant CDP WebSocket server on port 9222 — the same port and discovery surface Chromium exposes when launched with --remote-debugging-port=9222. The server implements Browser.*, Target.*, and the custom Lumabyte.* domain itself; every other command (Page, Runtime, DOM, Input, Network, Fetch, Emulation, Log, ~290 in total) forwards straight through Electron’s webContents.debugger to Chromium. What you don’t have to change:

• No new library. Keep your existing puppeteer, puppeteer-core, Playwright, chrome-remote-interface, pyppeteer, or chromedp client.
• The HTTP bootstrap surface matches Chromium. GET /json/version returns a webSocketDebuggerUrl. /json and /json/list enumerate targets. PUT /json/new?<url> opens a target. puppeteer.connect({ browserURL }) uses exactly these to discover the WebSocket endpoint.
• Flat-mode sessions, modern default. Target.setAutoAttach with flatten: true is supported, matching modern Puppeteer’s wire format.
• Browser contexts isolate state. Target.createBrowserContext returns a context ID that partitions cookies and storage (backed by a persistent persist:puppeteer-ctx-<id> partition).
• Native CDP is untouched. Network.setUserAgentOverride, Fetch.enable, Emulation.setDeviceMetricsOverride, DOMSnapshot.captureSnapshot — all pass through to Chromium the same way they would against chrome --headless.

Just change the launch:

// Downloads and launches bundled Chromium.
const puppeteer = require('puppeteer');

const browser = await puppeteer.launch({
  headless: 'new',
});

const page = await browser.newPage();
await page.goto('https://example.com');
console.log(await page.title());

await browser.close();

// LumaBrowser is already running. Attach.
const puppeteer = require('puppeteer-core');

const browser = await puppeteer.connect({
  browserURL: 'http://127.0.0.1:9222',
});

const page = await browser.newPage();
await page.goto('https://example.com');
console.log(await page.title());

await browser.disconnect();

That’s the entire migration. Swap puppeteer for puppeteer-core (no bundled Chromium), change launch(...) to connect({ browserURL }), point at port 9222. Everything below is what you gain by opting in.

Three concrete wins. Each one is opt-in: pay the cost only where you want the benefit.

Scrapers break when a marketing team renames a CSS class. LumaBrowser’s Lumabyte.* CDP domain retries the find via an LLM using a natural-language description of what the element is — not how it’s currently styled.

Two opt-in modes:

1. Keep your CSS, add a description fallback. Lumabyte.find({ description, selector }) tries the selector against DOM.querySelector first and only invokes the LLM when it misses. Happy-path scrapes cost nothing extra.
2. Skip CSS entirely. Lumabyte.find({ description }) or Lumabyte.click({ description }) lets the LLM own resolution end-to-end.

// Breaks the moment the button's class
// name changes during a UI refresh.
const puppeteer = require('puppeteer');

const browser = await puppeteer.launch();
const page = await browser.newPage();
await page.goto('https://example.shop/cart');

await page.waitForSelector(
  'button.btn-primary.signup'
);
await page.click('button.btn-primary.signup');

// LLM fallback re-resolves when CSS misses.
const puppeteer = require('puppeteer-core');

const browser = await puppeteer.connect({
  browserURL: 'http://127.0.0.1:9222',
});
const page = await browser.newPage();
await page.goto('https://example.shop/cart');

const cdp = await page.target().createCDPSession();
await cdp.send('Lumabyte.configureFallback', {
  enabled: true,
});

// Option A: keep CSS, add a description fallback.
await cdp.send('Lumabyte.click', {
  description: 'the sign-up button',
  selector:    'button.btn-primary.signup',
});

// Option B: skip CSS entirely.
await cdp.send('Lumabyte.click', {
  description: 'the sign-up button',
});

Classic Puppeteer agent loops make three separate CDP round-trips to capture page state: DOMSnapshot.captureSnapshot, then Accessibility.getFullAXTree, then Page.captureScreenshot. LumaBrowser’s Lumabyte.domSnapshot returns all three in a single call, ordered and correlated server-side.

// Three CDP round-trips per agent step.
const cdp = await page.target().createCDPSession();
await cdp.send('DOM.enable');
await cdp.send('Accessibility.enable');

const snapshot = await cdp.send(
  'DOMSnapshot.captureSnapshot',
  { computedStyles: [] }
);
const axTree = await cdp.send(
  'Accessibility.getFullAXTree'
);
const { data: screenshot } = await cdp.send(
  'Page.captureScreenshot',
  { format: 'png' }
);
// 3 requests, 3 responses, 3 places to retry.

// One call, server-correlated payload.
const cdp = await page.target().createCDPSession();

const { snapshot, axTree, screenshot } =
  await cdp.send('Lumabyte.domSnapshot', {
    includeAxTree:     true,
    includeScreenshot: true,
  });

// snapshot   — DOMSnapshot.captureSnapshot
// axTree     — Accessibility.getFullAXTree
// screenshot — base64 PNG of the viewport
// 1 request. Parse locally.

Classic puppeteer ships a ~170 MB Chromium binary per platform and launches it as a child process for every script run. That binary drifts behind Chrome stable, your CI downloads it on every cold cache, and the --user-data-dir left behind needs cleanup. LumaBrowser’s CDP server runs inside the browser process itself — there is no binary to download, no launcher lifecycle, no temp profile to reap.

And unlike attaching to a user’s regular Chrome (where your automation would fight for the same tabs the user is browsing in), LumaBrowser gives the CDP client dedicated automation tabs: only tabs created with kind: 'puppeteer' surface as CDP targets, rendered in the tab strip with a purple accent and a PUP badge so you can watch the session drive them live.

// puppeteer ships a bundled Chromium and
// spawns it as a child process on every run.
const puppeteer = require('puppeteer');

const browser = await puppeteer.launch({
  headless: 'new',
  args: ['--no-sandbox'],
  userDataDir: '/tmp/pup-profile',
});

// Plus: Chromium version drift, ~170MB
// per-platform binary, child-process cleanup,
// stale --user-data-dir trees, and the
// occasional "Failed to launch the browser
// process!" at 3am.

// LumaBrowser is already running. Attach.
const puppeteer = require('puppeteer-core');

const browser = await puppeteer.connect({
  browserURL: 'http://127.0.0.1:9222',
});

// Dedicated "PUP" tabs, visible in the strip.
// No binary download.
// No child process.
// No --user-data-dir to clean up.
// The user's regular tabs stay invisible to
// the CDP client, so Network Interceptor and
// AI Chat don't fight for the debugger lock.

What a realistic flow looks like when you mix native CDP with Lumabyte.*. Notice how close the code reads to the task description.

const puppeteer = require('puppeteer-core');

// 1. Attach to the already-running browser.
const browser = await puppeteer.connect({
  browserURL: 'http://127.0.0.1:9222',
});
const page = await browser.newPage();
await page.goto('https://example.shop/products/coffee-grinder');

const cdp = await page.target().createCDPSession();

// 2. Opt in to LLM fallback for this session.
await cdp.send('Lumabyte.configureFallback', {
  enabled:            true,
  onFindFail:         true,   // retry failed finds via LLM
  onClickIntercepted: true,   // retry intercepted clicks via LLM
});

// 3. Describe elements, don't select them.
await cdp.send('Lumabyte.click', { description: 'the add-to-cart button' });
await cdp.send('Lumabyte.click', { description: 'the cart icon in the header' });

// 4. Pull DOM + AX tree + screenshot in one round-trip.
const { snapshot, axTree, screenshot } = await cdp.send('Lumabyte.domSnapshot', {
  includeAxTree:     true,
  includeScreenshot: true,
});

// 5. Native CDP still works — verify via Runtime.evaluate.
const { result } = await cdp.send('Runtime.evaluate', {
  expression:    'document.title',
  returnByValue: true,
});
console.log(result.value);

await browser.disconnect();

Twenty-odd lines, zero brittle CSS, one round-trip to capture the page state for your agent loop or visual diff. Try writing the same flow in classic Puppeteer and count the selectors you’d need to maintain next quarter.

What works today against the puppeteer-driver extension, and where the additions sit:

If your workflow needs Network.* or Fetch.* request interception, it just works — those domains forward straight to Chromium. The Lumabyte.* additions are purely additive; existing Puppeteer code ignores them and keeps running.

Two ways, takes under a minute either way:

1. From the UI

1. Open Settings → Puppeteer.
2. (Optional) Check “Start automatically when LumaBrowser launches.”
3. Click Save & Start.
4. Point your Puppeteer client at http://127.0.0.1:9222.

2. Via the REST API

# Start the CDP server
curl -X POST http://localhost:3000/api/puppeteer/start

# Check status
curl http://localhost:3000/api/puppeteer/status

# Bind to all interfaces on a custom port
curl -X POST http://localhost:3000/api/puppeteer/settings \
  -H "Content-Type: application/json" \
  -d '{"host": "0.0.0.0", "port": 9333}'

For the full CDP domain reference, Lumabyte.* method signatures, and MCP tool surface, see the Puppeteer Driver section of the API docs.

Install LumaBrowser, enable the puppeteer-driver extension, and swap puppeteer.launch() for puppeteer.connect({ browserURL: 'http://127.0.0.1:9222' }). Every native CDP command keeps working. The Lumabyte.* domain is there when you want it.