Codex App settings shows Chrome extension disconnected while the extension backend is usable from another Chrome profile

What version of the Codex App are you using (From “About Codex” dialog)?

Codex App package observed on Windows: 26.602.3474.0Chrome plugin bundle: 26.602.30954Codex Chrome Extension: 1.1.5_0

What subscription do you have?

Unknown

What platform is your computer?

Windows 10 Pro 10.0.19045 x64

What issue are you seeing?

The Codex App settings page reports that the Codex Chrome Extension is not connected, but the extension backend is actually available and usable from the current browser session.

In this environment, the state differs by Chrome profile:

• Google Chrome stable default profile:
• User data dir: %LOCALAPPDATA%/Google/Chrome/User Data/Default
• Codex Chrome Extension is not installed.
• Chrome Dev default profile:
• User data dir: %LOCALAPPDATA%/Google/Chrome Dev/User Data/Default
• Codex Chrome Extension is installed but disabled.
• Currently running Chrome Dev temporary profile:
• User data dir: %TEMP%/chrome-debug/Default
• Codex Chrome Extension is installed and enabled.
• Native messaging host starts successfully.
• Codex can discover the extension browser backend and communicate with it.

After reinitializing browser discovery, agent.browsers.list() includes an extension backend:

{
  "type": "extension",
  "name": "Chrome",
  "metadata": {
    "extensionId": "hehggadaopoacecdllhhajmbjkdcmajg"
  }
}

A lightweight communication check also succeeds:

{
  "extensionCommunication": {
    "ok": true,
    "tabCount": 5
  }
}

However, the Codex App settings UI still shows the Chrome extension as disconnected.

What steps can reproduce the bug?

1. Run Chrome Dev with a temporary user data directory, for example a chrome-debug profile.
2. Install and enable the Codex Chrome Extension in that running temporary Chrome Dev profile.
3. Leave Google Chrome stable's default profile without the extension installed.
4. Ensure the native messaging manifest is installed and valid.
5. Trigger Codex browser discovery / use the Chrome extension backend.
6. Observe that the extension backend is discovered and usable.
7. Open Codex App settings and check the Chrome extension connection status.

Observed result:
The extension backend is usable, but the settings UI still reports the extension as disconnected.

Likely cause:
The settings/install check appears to inspect the stable Chrome default profile rather than the live connected extension backend, or it does not account for Chrome Dev / non-default user data directories.

What is the expected behavior?

The Codex App settings page should reflect the actual connected extension backend state, or clearly indicate which Chrome installation/profile it is checking.

If the extension is connected from Chrome Dev or a non-default user data directory, the UI should not simply report "disconnected" without explaining the profile mismatch.

Additional information

_No response_