[macOS Desktop] In-app Browser control unavailable because bundled node_repl MCP client never becomes ready
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using?
Codex Desktop 26.803.61601 (build 6396), Chromium 151.0.7922.76.
Platform
macOS, Apple Silicon (arm64).
What issue are you seeing?
The in-app Browser opens pages normally, but Codex cannot inspect, click, type, or otherwise control the page because the bundled Browser/Computer Use MCP tool is absent from the task.
The same setup worked on 2026-08-13. Beginning on 2026-08-14, Browser control stopped working and remains unavailable after fully quitting and restarting Codex multiple times.
Local logs repeatedly show:
omitting MCP server without an exact ready client server_name=node_repl
The previous working session logged successful initialization of the same service:
server_name=node_repl ... Service initialized as client ... version 1.5.0
Other MCP services initialize normally in the failing sessions. The bundled Browser plugin is enabled, its files are present, the configured node_repl executable exists and responds to --help, and the target web origin is allowed. No Browser/Computer Use tool is exposed to the task.
No private page content, credentials, complete configuration files, or raw log database are attached publicly.
Steps to reproduce
- Open Codex Desktop on macOS.
- Open a page in the in-app Browser.
- In a task, reference Browser and ask Codex to inspect the current page title or click/type on the page.
- Observe that no Browser/Computer Use MCP tool is available.
- Fully quit Codex Desktop and reopen it.
- Create a new task and repeat.
- Observe that the failure persists and the log contains:
omitting MCP server without an exact ready client server_name=node_repl.
Expected behavior
The bundled node_repl MCP client should initialize and expose the Browser/Computer Use tools, allowing Codex to inspect and interact with the in-app Browser.
Actual behavior
The in-app Browser renders pages, but the control bridge never becomes ready. Codex omits the node_repl server from the tool catalog, so page inspection and interaction are impossible.
Additional information
- This worked on the same installation on 2026-08-13.
- It failed on 2026-08-14 without an intentional configuration change.
- Full application restarts do not recover it.
- The target site's login and page rendering still work; only the control interface is unavailable.
- Related but not identical: #38342 (plugin skill present while its stdio MCP tools are absent). This report concerns the bundled Browser/Computer Use
node_replservice.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the bundled node_repl initialization around the log message omitting MCP server without an exact ready client server_name=node_repl, then compare it with the earlier successful initialization. Reproduce on macOS with the in-app Browser and verify that the client reaches ready state and Browser/Computer Use tools appear in the task.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, node.js, rust
- Domain
- desktop, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100