Codex / AI Coding Tools

Codex Desktop Browser Use Broken After Update — Node REPL Not Discovered

Fix Codex Desktop Browser Use not working after update — Node REPL execution tool not exposed Includes evidence for Codex troubleshooting demand.

Source-backed Last updated May 12, 2026 1 source Needs local verification

Category: AI Coding Tools
Error signature: Browser Use broken: no node_repl/js or no Codex IAB backend discovered
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: May 12, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for Codex, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

Browser Use broken: no node_repl/js or no Codex IAB backend discovered is a Codex failure pattern reported for developers trying to fix codex desktop browser use not working after update — node repl execution tool not exposed. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

After Codex Desktop update on macOS, Browser Use feature broken. In-app browser open on local dev server, but Browser Use commands fail because Node REPL execution tool not exposed. Tool discovery for mcp__node_repl fails. Affects macOS users specifically.

Common causes

Codex Desktop is OpenAI's AI coding IDE. Browser Use is a key feature for web automation tasks. After an update, the main thread can no longer discover the Node REPL execution tool (mcp__node_repl), breaking browser automation workflows that developers rely on for testing and scraping.
After Codex Desktop update on macOS, Browser Use feature broken. In-app browser open on local dev server, but Browser Use commands fail because Node REPL execution tool not exposed. Tool discovery for mcp__node_repl fails. Affects macOS users specifically.

Quick fixes

Confirm the exact error signature matches Browser Use broken: no node_repl/js or no Codex IAB backend discovered.
Check the Codex account, local tool state, and provider configuration involved in the failing workflow.
Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match Browser Use broken: no node_repl/js or no Codex IAB backend discovered exactly before applying the quick fix.
Compare the failing environment with Codex versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does Browser Use broken: no node_repl/js or no Codex IAB backend discovered mean in Codex?

Browser Use broken: no node_repl/js or no Codex IAB backend discovered indicates the workflow described by "Codex Desktop Browser Use Broken After Update — Node REPL Not Discovered" failed in a AI Coding Tools context. Start by confirming the exact signature and the component that emitted it.

What should I check first for Browser Use broken: no node_repl/js or no Codex IAB backend discovered?

Check whether this cause matches your environment: Codex Desktop is OpenAI's AI coding IDE. Browser Use is a key feature for web automation tasks. After an update, the main thread can no longer discover the Node REPL execution tool (mcp__node_repl), breaking browser automation workflows that developers rely on for testing and scraping.

Is the Browser Use broken: no node_repl/js or no Codex IAB backend discovered guidance source-backed?

The "Codex Desktop Browser Use Broken After Update — Node REPL Not Discovered" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for Browser Use broken: no node_repl/js or no Codex IAB backend discovered?

For "Codex Desktop Browser Use Broken After Update — Node REPL Not Discovered", avoid applying "Compare the failing environment with a known working setup, then change one configuration value at a time." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging Browser Use broken: no node_repl/js or no Codex IAB backend discovered?

For "Codex Desktop Browser Use Broken After Update — Node REPL Not Discovered", collect the failing Codex command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.