Puppeteer: To use `enableExtensions` with a list of paths in Chrome, you must be connected with `--remote-debugging-pipe` (`pipe: true`).

Chrome extension-path installation requires remote-debugging-pipe transport.

Error message

To use `enableExtensions` with a list of paths in Chrome, you must be connected with `--remote-debugging-pipe` (`pipe: true`).

How this error happens

Loading an explicit list of Chrome extension paths requires Puppeteer’s remote-debugging-pipe connection. Omitting that transport fails the launch requirement.

The snippets use the imported puppeteer instance.

await puppeteer.launch({
    browser: "chrome",
    enableExtensions: [
        "/absolute/path/unpacked-extension",
    ],
});

How to fix

Enable pipe transport while preserving the extension list.

const browser = await puppeteer.launch({
    browser: "chrome",
    pipe: true,
    enableExtensions: [
        "/absolute/path/unpacked-extension",
    ],
});

Things to keep in mind

The path must contain a real unpacked extension. A missing or invalid extension directory produces a different error. Firefox/BiDi pipe limitations are separate.

All Puppeteer errors