Browser Use unavailable: node_repl / JavaScript execution tool not exposed despite Browser plugin installed

Open 💬 2 comments Opened May 8, 2026 by michaelplzno

Environment:

  • OS: Windows 11
  • IDE: VS Code
  • Codex surface: VS Code extension / Codex app [choose whichever applies]
  • Codex version: [paste from About Codex or codex --version]
  • Browser Use plugin: installed and available
  • Workspace type: [native Windows / WSL / remote / other]

Issue:
Browser Use appears installed and the required client script exists, but Codex cannot drive the in-app browser because the required Node REPL / JavaScript execution tool is not exposed in the session.

Observed state:

  • Browser Use plugin: installed and available
  • Required client script: present at browser-client.mjs
  • Required runtime tool: node_repl / JavaScript execution is not currently exposed in this session, even after tool discovery
  • Searches for node_repl, js, JavaScript execution, and browser runtime tools find no callable tool

Expected:
When Browser Use is enabled and browser-client.mjs exists, Codex should expose the required node_repl/js or mcp__node_repl__js tool, or show a clear diagnostic explaining why it failed to load.

Actual:
The Browser plugin is installed, but Codex cannot bootstrap the in-app browser because the Node REPL tool is missing from the session.

Troubleshooting already tried:

  • Restarted Codex multiple times
  • Restarted VS Code
  • Confirmed Browser Use plugin is installed
  • Confirmed browser-client.mjs exists
  • Started new sessions/threads
  • Tool discovery still does not expose node_repl/js

Impact:
Codex can inspect files and run shell commands, but cannot test local web pages through the in-app browser. Browser-based verification has to fall back to Playwright or manual testing.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗