Browser Automation - Linux Install Path

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hi there,

I’m working with Cursor (2.0.43) and connecting to Ubuntu (WSL2). Google Chrome confirmed installed (google-chrome --version),

I’ve added the install path “/opt/google/chrome/chrome” to Tools → Browser Automation. The purpose to begin looking at headless testing etc. on Linux.

It comes back with the message “Chrome not found”. @Browser also now brings up the error to install Chrome.

Am I missing something here with my specification of the path, or some other issue to make the configuration work?

Many thanks,

Justin

Steps to Reproduce

  1. Open Cursor Settings
  2. Choose Tools & MCP
  3. Select Browser Automation.
  4. Set Connection Type to “Custom Executable Path”: /opt/google/chrome/chrome

Expected Behavior

I should be able to use the @Browser tool and create agents to perform background research with the tool.

Screenshots / Screen Recordings

Screenshot-2025-11-02 070314.png
Screenshot-2025-11-02 070314.png586×249 7.35 KB

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.43 (user setup)
VSCode Version: 1.99.3
Commit: 8e4da76ad196925accaa169efcae28c45454cce0
Date: 2025-10-30T18:49:27.589Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.22621

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

Hey, thanks for the report. There are two issues:

  1. WSL2 remote development limitation
    Browser Automation currently expects Chrome to be installed on the Windows host, not inside WSL2. Since you connect to WSL2 from Windows, Cursor looks for Chrome on Windows, not Ubuntu.

Temporary workaround: Install Chrome on Windows. Cursor should detect it automatically if it’s in a standard path like C:\Program Files\Google\Chrome\Application\chrome.exe.

  1. Custom path bug
    Multiple users report that the “Custom Executable Path” setting added in v2.0 is being ignored across platforms.

Could you confirm:

  • Is Chrome installed on the Windows host?
  • Do you specifically need Chrome in WSL2 for headless tests?

Let me know if installing Chrome on Windows helps as a temporary workaround.

1 Like
3

Hi @deanrie ,

No worries, thank you for the response.

Chrome is on Windows, here: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe. Chrome is also installed on the WSL2 image. Here are my observations:

  1. WSL2 - OK, is “Default (Bundled Chrome)” the standard executable in a predictable location, e.g. C:\Program Files (x86)\Google\Chrome\Application\chrome.exe ?
  2. If I inspect “Browser Automation” in Cursor Settings, while working with WSL2, whether I use a Windows path, as above, or a Linux path as per the initial report it STILL does not find a chrome.exe install (Windows or WSL2 Linux).

So, in the chat I can connect to a “Browser Tab” (see attached image), which makes me understand it is finding a browser somewhere for the web capability, but cannot use the “@Browser” tool since it requests the chrome install.

In my case, I can live with using the browser tab for now. It would be nice to understand that in the roadmap some-place there is a spot for “fuller automation” of browser tasks from the agent chat.

For now, continuing to explore established frameworks for web-app testing works fine. :slight_smile:

Hope this helps,

Justin

image
image112×117 2.4 KB

4

Thanks for the info, that’s very helpful.