codex - 💡(How to fix) Fix Browser plugin bootstrap fails in Codex App: browser-client is not trusted

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…

Browser plugin / in-app browser automation fails during bootstrap in the Codex desktop app.

Error Message

privileged native pipe bridge is not available; browser-client is not trusted

Root Cause

Browser plugin / in-app browser automation fails during bootstrap in the Codex desktop app.

Code Example

privileged native pipe bridge is not available; browser-client is not trusted
RAW_BUFFERClick to expand / collapse

Summary

Browser plugin / in-app browser automation fails during bootstrap in the Codex desktop app.

Environment

  • Codex App version: 26.527.31326
  • Thread id: 019e7814-b976-73a0-aaa2-36cc02b620be
  • This thread is being used from the Codex desktop app, not only from CLI/cmux.

Error

privileged native pipe bridge is not available; browser-client is not trusted

Minimal checks

  • The in-app browser itself is visible in the Codex App UI.
  • Browser skill bootstrap uses an absolute path import for browser-client.mjs.
  • No localhost navigation, URL transition, tab creation, or real UI inspection was attempted.
  • nodeRepl exists.
  • nodeRepl.nativePipe is false / missing.
  • requestMeta keys are only progressToken, threadId, and x-codex-turn-metadata.
  • Browser backend metadata is not visible in request metadata.
  • Computer Use has worked separately in a Codex App session with list_apps.

Current diagnosis

The trusted native bridge / browser backend metadata for the Browser plugin appears not to be injected into this thread's Node REPL runtime, even though the thread is being used from the Codex desktop app and the in-app browser is visible.

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

codex - 💡(How to fix) Fix Browser plugin bootstrap fails in Codex App: browser-client is not trusted