codex - 💡(How to fix) Fix In-app browser inspection is blocked when node_repl requires Node >= 22.22.0 but desktop environment resolves Node 18 [1 comments, 2 participants]

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…
GitHub stats
openai/codex#21246Fetched 2026-05-06 06:24:15
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Timeline (top)
labeled ×5commented ×1cross-referenced ×1

Error Message

Error shown

Root Cause

What happened?

While trying to inspect the currently selected in-app browser tab from Codex desktop, the browser-use workflow could not start because the node_repl runtime resolved the local Node installation at:

RAW_BUFFERClick to expand / collapse

What version of Codex is running?

Unknown from UI; observed on May 5, 2026 in the Codex desktop app on Windows.

Which model were you using?

GPT-5 based Codex coding agent in the desktop app.

What platform is your computer?

Windows

What happened?

While trying to inspect the currently selected in-app browser tab from Codex desktop, the browser-use workflow could not start because the node_repl runtime resolved the local Node installation at:

C:\Program Files\nodejs\node.exe

That runtime was version:

v18.17.1

The tool reported that it requires:

>= v22.22.0

As a result, in-app browser inspection was blocked even though the browser tab was already open and the Browser Use plugin was available.

Error shown

Node runtime too old for node_repl (resolved C:\Program Files\nodejs\node.exe): found v18.17.1, requires >= v22.22.0. Install/update Node or set NODE_REPL_NODE_PATH to a newer runtime.

Steps to reproduce

  1. Open Codex desktop on Windows.
  2. Have a browser tab open in the in-app browser.
  3. Ask Codex to inspect or interact with the current browser tab using the Browser Use workflow.
  4. Observe that the workflow fails before inspecting the tab because node_repl resolves an older system Node runtime.

Expected behavior

Codex desktop should either:

  • bundle or use a compatible Node runtime for node_repl, or
  • gracefully fall back without blocking browser inspection, or
  • provide a clearer setup path before browser tooling is attempted.

Actual behavior

Browser inspection fails immediately due to a Node version dependency mismatch in the local environment.

Additional context

This came up while trying to inspect an already open Codex browser tab and correlate an uploaded feedback report with thread ID:

019df9f1-7d90-7950-8e06-b329535708db

The issue appears to be environmental/dependency-related rather than specific to the page content being inspected.

extent analysis

TL;DR

Update the Node.js version to at least v22.22.0 to resolve the node_repl runtime compatibility issue.

Guidance

  • Verify the current Node.js version installed on the system using the command node -v in the terminal or command prompt.
  • Check if there are multiple versions of Node.js installed on the system and ensure that the correct version is being used by node_repl.
  • Consider setting the NODE_REPL_NODE_PATH environment variable to point to a newer Node.js runtime if updating the system-wide Node.js version is not feasible.
  • Ensure that the Codex desktop app is configured to use the updated Node.js version after installation.

Example

No code snippet is necessary for this issue, as it is related to environment configuration.

Notes

The issue is specific to the Windows platform and the Codex desktop app, and may not apply to other environments or versions of Codex.

Recommendation

Apply the workaround by updating the Node.js version to at least v22.22.0, as this is the minimum required version for node_repl to function correctly.

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…

FAQ

Expected behavior

Codex desktop should either:

  • bundle or use a compatible Node runtime for node_repl, or
  • gracefully fall back without blocking browser inspection, or
  • provide a clearer setup path before browser tooling is attempted.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING