Puppeteer: Missing browser context

A CDP target has no matching browser context in the registry.

Error message

Missing browser context

How this error happens

A target’s context ID had no matching BrowserContext in Puppeteer’s registry. This is an internal initialization or registry check, not an application input validator.

Use a running Chrome/CDP browser named browser. The following is a lifecycle race to rule out.

const context = await browser.createBrowserContext();

await Promise.all([
    context.newPage(),
    context.close(),
]);

Creation and shutdown overlap in this example. Depending on event order, Puppeteer may report a target/session-closed error instead. It is not a deterministic reproduction of this particular registry message.

How to fix

Keep the browser and context alive until creation and page work finish. Run the corrected sequence with a fresh live browser.

const context = await browser.createBrowserContext();

try {
    const page = await context.newPage();

    await page.setContent(
        "<p>Context task</p>"
    );
} finally {
    await context.close();
}

Things to keep in mind

If this exact initialization error persists with sequential public API calls, retain the full stack and a minimal reproduction and report the browser/Puppeteer failure. Do not manufacture target IDs, initialize private maps, or retry an external side effect blindly.

All Puppeteer errors