codex - 💡(How to fix) Fix [Windows] Browser plugin fails with "browser-client is not trusted" despite advertised chrome and iab backends

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Both fail with the same trust/native pipe error.

Fix Action

Fix / Workaround

Workaround: direct Playwright execution works against the same target.

RAW_BUFFERClick to expand / collapse

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

26.506.2212.0

What subscription do you have?

Pro

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

The Codex Desktop Browser / browser-use plugin fails with:

privileged native pipe bridge is not available; browser-client is not trusted
This happens even though the Node REPL request metadata advertises both chrome and iab as available browser backends.

The issue appears to be with the Browser plugin runtime or Node REPL trusted native pipe injection, not with the local web app being tested. Direct Playwright automation against the same localhost URL works.

Diagnostics observed from Node REPL:

{
  "hasNativePipe": false,
  "requestMeta": {
    "x-codex-browser-use-available-backends": [
      "chrome",
      "iab"
    ]
  }
}
Additional observations:

x-codex-browser-use-available-backends includes chrome and iab
import.meta.__codexNativePipe is not available
\\.\pipe\codex-browser-use-* pipes exist
~/.codex/config.toml has the Browser plugin enabled
The local app is reachable over HTTP
Direct Playwright Chromium automation against the same URL succeeds

### What steps can reproduce the bug?

Uploaded thread: daff1fa5-966b-436a-8791-682411321073
*To Codex dev teams, reference this id. You have my submitted logs.

Start Codex Desktop on Windows.
Use the bundled Browser plugin:
browser-use@openai-bundled
observed path: ~/.codex/plugins/cache/openai-bundled/browser-use/0.1.0-alpha2/
In the Node REPL, run:
const { setupAtlasRuntime } = await import(
  "file:///C:/Users/ms-ef/.codex/plugins/cache/openai-bundled/browser-use/0.1.0-alpha2/scripts/browser-client.mjs"
);

await setupAtlasRuntime({ globals: globalThis });
const browser = await agent.browsers.get("chrome");
Repeat with iab:
const browser = await agent.browsers.get("iab");
Both fail with the same trust/native pipe error.

### What is the expected behavior?

What is the expected behavior?
If chrome or iab is advertised as an available backend, Browser plugin setup should succeed:

await setupAtlasRuntime({ globals: globalThis });
const browser = await agent.browsers.get("chrome");
// or
const browser = await agent.browsers.get("iab");
After setup, browser navigation, DOM snapshots, screenshots, clicks, and reloads should work.

### Additional information

Workaround: direct Playwright execution works against the same target.

npx -y playwright install chromium
npx -y playwright screenshot --browser chromium "http://127.0.0.1:59832/?sample=web-edited-sales&v=type-old-new-layout" tmp/page.png
A temporary Node runner with the playwright package also works for multi-step UI checks.

Suspected cause: the browser backends are detected, but the current Node REPL runtime is not receiving the trusted native pipe bridge. This looks like a Codex Desktop / Browser plugin runtime initialization issue, or a failure to inject import.meta.__codexNativePipe into the Node REPL environment.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING