Cursor ignores Chrome Executable Path

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Chrome Executable Path is simply always ignored.
The default option is used instead.

The “Refresh Status” button does not produce any visual errors.
It says: “Ready (Chrome detected)”

When I ask Cursor to open the web-browser and navigate to: localhost:3000 I see that it uses it’s own Chrome installation.

I am able to confirm this because my own installation has custom backgrounds, certs preinstalled etc that the default bundled Chrome does not.

Problem I am trying to solve: To have the chrome instance have preinstalled certs, so I can use HTTPS.
I am unable to have the default Chrome instance use those. So I need my own instance of Chrome for Cursor to use.

Steps to Reproduce

  1. Use a Linux machine, for me Ubuntu (unaware if it works on windows).
  2. Add a path to Chrome Executable Path
  3. Press “Refresh Status”
  4. See that Cursor says the Chrome installation is ready to use.
  5. Task AI agent to open a web-browser window.
  6. See that the browser being used is definitely not the one you pointed the IDE to.

Expected Behavior

I can see that the opened browser is from the path that was given to Cursor.

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.77
VSCode Version: 1.99.3
Commit: ba90f2f88e4911312761abab9492c42442117cf0
Date: 2025-11-13T23:10:43.113Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Linux x64 6.14.0-35-generic Ubuntu 24

For AI issues: which model did you use?

Auto

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

Hey, thanks for the report. This is a known issue: the Custom Executable Path setting for Browser Automation is currently ignored on all platforms, including native Linux installs.

Temporary workaround: while this is being fixed, you can use the “Browser Tab” option in Agent chat (it appears as a tool choice in the chat UI). It has less functionality than @browser, but it may work for basic browsing tasks.

I understand this doesn’t solve your need for pre-installed certs in HTTPS testing. The engineering team is aware of this requirement and is actively working on a fix.

1 Like
3

I find it really nice that I spent about 5 hours debugging this…
Why push a feature that does not work, I just don’t get it.
This is not how you do software development, do you guys not have automated tests?

4

But thanks for getting back to me, now I know.
A fun story to tell my coworkers…