Windows desktop: @Chrome mention lacks tabId/providerTabId and cannot bind the current Chrome tab

Description

On Windows, Codex Desktop cannot bind or read the current Chrome tab through the bundled @Chrome integration.

The generated Chrome mention contains only:

plugin://browser@openai-bundled?browserFamily=chrome

It does not contain a tabId or providerTabId.

The operation then fails with:

• Invalid tab mention fields
• nodeRepl.fetch request failed

Steps to reproduce

1. Open a webpage in Chrome, for example https://www.baidu.com.
2. Open Codex Desktop.
3. Add the @Chrome mention in the message composer.
4. Ask Codex to read the title of the current Chrome tab.
5. Observe that no page content or title is returned.

Expected behavior

Codex should bind the selected/current Chrome tab. The tab mention should contain a valid tabId or providerTabId, and Codex should be able to read the page title and content.

Actual behavior

The mention contains only browserFamily=chrome. Codex cannot identify a specific tab and reports Invalid tab mention fields or nodeRepl.fetch request failed.

Diagnostics already completed

• Chrome extension is enabled.
• Extension version: 1.26.901.11451
• Extension has access to all sites.
• The native messaging host is registered and running.
• The extension Service Worker starts normally and shows no console errors.
• Chrome, the extension, and Codex Desktop have all been restarted.
• The extension was also manually reloaded.
• The problem remains unchanged after restarting.
• During reproduction, the extension Service Worker receives no event.

The lack of Service Worker activity suggests that the request fails in the Codex Desktop tab-reference or browser-bridge layer before reaching the Chrome extension.

Versions

• Codex Desktop: 26.915.4065
• Bundled Chrome plugin: 26.915.31945
• Chrome extension: 1.26.901.11451
• Google Chrome: 152.0.7977.83
• Codex CLI: 0.145.0
• OS: Windows

Feedback session

A feedback report containing the associated Codex session has already been submitted.

Session ID: 01a0ba6c-b56e-7020-b934-374628ac2ec9

Start by tracing the Windows Codex Desktop tab-reference and browser-bridge path that constructs the @Chrome mention, then reproduce the issue with the supplied Chrome and Codex versions. Identify why tabId or providerTabId is omitted before the Chrome extension receives a request; done means the mention identifies the current tab and Codex can read its title and content without the reported errors.