codex - 💡(How to fix) Fix Chrome plugin: tab.goto() causes native pipe closed / kernel reset, blocking navigation and web automation

node_repl kernel unhandled rejection: native pipe is closed; kernel reset.
This blocks the Chrome plugin from doing the main tasks I need:

Opening web pages
Searching the web
Reading search results
Filling forms
Opening Gmail or other webmail
Completing multi-step browser workflows
Environment checks pass:

Chrome is running.
Codex Chrome Extension is installed and enabled.
Native host manifest exists and is correct.
Registry native messaging host path matches the manifest.
So this does not look like an authorization issue or a website-specific issue. It looks like a Chrome Extension / native messaging / browser-client navigation stability issue.

### What steps can reproduce the bug?

1. Start Codex with the Chrome plugin enabled.

2. Connect to Chrome through the plugin.

3. Verify that basic tab listing works:

```js
const { setupBrowserRuntime } = await import('file:///C:/Users/Admin/.codex/plugins/cache/openai-bundled/chrome/0.1.7/scripts/browser-client.mjs');
await setupBrowserRuntime({ globals: globalThis });
globalThis.browser = await agent.browsers.get('extension');
await browser.nameSession('Chrome capability test');

const openTabs = await browser.user.openTabs();
console.log(openTabs);
This succeeds.

4.Create a managed tab:
globalThis.tab = await browser.tabs.new();
console.log(await tab.title(), await tab.url());
This succeeds and returns an about:blank tab.

5.Try to navigate the managed tab:
await tab.goto('https://example.com/');
await tab.playwright.waitForLoadState({ state: 'domcontentloaded', timeoutMs: 15000 });
The Node REPL kernel crashes/resets with:
node_repl kernel unhandled rejection: native pipe is closed; kernel reset.
Additional observations:

6.The same issue happened when navigating to a localhost page:
http://127.0.0.1:8765/chrome-test-form.html
Trying to claim chrome://newtab/ failed with:
Chrome internal tab 1709557289 cannot be claimed
Using CUA keyboard actions to press Ctrl+L, type a URL, and press Enter returned without an error, but the tab stayed on about:blank.

### What is the expected behavior?

The Chrome plugin should be able to navigate a managed tab to normal web pages such as `https://example.com/`, then allow Playwright/DOM operations on that page.

Expected workflow:
1. Create or claim a controllable Chrome tab.
2. Navigate to a URL.
3. Wait for the page to load.
4. Read DOM content.
5. Fill forms.
6. Click buttons.
7. Continue multi-step workflows such as search, web forms, or email drafting.

If navigation fails, it should fail as a normal catchable JavaScript exception instead of closing the native pipe and resetting the Node REPL kernel.

### Additional information

_No response_