Chrome backend unavailable in terminal/API session: untrusted-code-signing-identity while Codex App @Chrome works

Summary

Chrome integration works from Codex App, but the terminal/API Codex session cannot discover or use the Chrome backend.

The Chrome extension itself appears healthy:

• Chrome extension popup shows Connected
• Chrome extension version: 1.1.5
• Chrome extension ID: hehggadaopoacecdllhhajmbjkdcmajg
• Chrome extension details show it is enabled
• Site access is set to all websites
• Service Worker console is empty
• Codex App settings show Computer Use > Google Chrome connected

However, a terminal/API Codex session cannot access the Chrome backend and reports:

Browser is not available: extension

agent.browsers.list() returns:

[]

Environment

• macOS arm64
• Codex app/plugin version: 26.623.61825
• Chrome extension: Codex v1.1.5
• Chrome extension ID: hehggadaopoacecdllhhajmbjkdcmajg
• Chrome profile: Default
• Native host manifest check: passed
• Extension installed/enabled check: passed

What works

In Codex App, @Chrome can open a local page using the real Chrome profile and logged-in state.

The Chrome extension popup shows Connected, and Codex App settings show Google Chrome as connected.

What fails

In a terminal/API Codex session, attempting to use the Chrome backend fails:

Browser is not available: extension

The browser list is empty:

[]

Relevant logs

Codex App logs include:

browser-use native pipe peer authorization failed
failed to read peer code signing identity
browser-use native pipe rejected socket peer reason=untrusted-code-signing-identity

Earlier behavior was similar to missing-code-signing-identity, but the current observed reason is untrusted-code-signing-identity.

Steps already tried

1. Confirmed Chrome is running.
2. Confirmed Codex Chrome extension is installed and enabled.
3. Confirmed native host manifest exists and matches expected origin:

chrome-extension://hehggadaopoacecdllhhajmbjkdcmajg/

1. Restarted Chrome and Codex App.
2. Reinstalled the Chrome plugin from Codex Plugins.
3. Reinstalled/refreshed the Chrome extension.
4. Started a new Codex session.
5. Reset/reloaded the browser runtime using the latest plugin path.
6. Checked the Chrome extension Service Worker console; no obvious extension-side error.

Expected behavior

Either:

• terminal/API Codex sessions should be able to use the same connected Chrome backend as Codex App, or
• the product should clearly document that Chrome backend access is only supported from Codex App threads and not from terminal/API sessions.

Actual behavior

Codex App @Chrome works, but the terminal/API session cannot access Chrome and fails with a local pipe code-signing authorization error.

Feedback ID

Submitted through Codex App feedback:

019f1286-40fc-7b92-ba40-24ef4a5778e8

Possibly related issues

• #30155
• #21719