run-code command fails with "page is undefined" in --extension mode

[gslvly]

Description

When using playwright-cli open --extension, the run-code command fails with page is undefined error.

Reproduction Steps

1. Run: playwright-cli open --extension
2. Select a tab in the browser (with existing logged-in session)
3. Run: playwright-cli run-code "async page => { await page.waitForLoadState('networkidle'); return await page.evaluate(() => document.body.innerText); }"

Expected Behavior

The page parameter should be available in the callback function, allowing Playwright API calls like page.waitForLoadState(), page.evaluate(), etc.

Actual Behavior

Error: page is undefined

Root Cause Analysis

Looking at the source code:

1. In lib/mcp/browser/tools/runCode.js:56-58:

const context = {
  page: tab.page,
  __end__
};

2. tab.page comes from Tab class initialization in lib/mcp/browser/tab.js:49

3. In --extension mode, the browser context is created via ExtensionContextFactory (see lib/mcp/program.js:64-70)

4. The Tab object may not be properly initialized via _onPageCreated callback when connecting to an existing browser tab through the extension.

Impact

This prevents users from:

• Using run-code to execute Playwright API calls in extension mode
• Waiting for page states (e.g., waitForLoadState('networkidle'))
• Executing complex page evaluations

Workaround

• Use normal mode without --extension flag
• Use state-save/state-load to transfer authentication state between sessions

Environment

• playwright-cli version: 0.1.1
• playwright version: 1.59.0-alpha
• Node.js: v22.20.0
• OS: macOS (darwin)

Related Issues

• Feature Request: extension mode support #211 - Feature Request: extension mode support
• Extension seems broken again #254 - Extension seems broken again
• 'playwright-cli --extension open' does not play well with PLAYWRIGHT_MCP_EXTENSION_TOKEN #267 - --extension does not play well with PLAYWRIGHT_MCP_EXTENSION_TOKEN
• eval with arrow function produces "TypeError: result is not a function" #296 - eval with arrow function produces error (similar workaround suggested)

[yury-s]

I was not able to reproduce it:

playwright-cli open playwright.dev --extension --browser=chrome-canary 
playwright-cli run-code "async page => { return await page.evaluate(() => document.body.innerText); }"

Does the page stay open? Can you share exact commands where it happens?