Cursor Browser doesn't support Google Chrome Portable

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Google Chrome Portable is the portable version of Chrome, but it’s not detected by Cursor.

Steps to Reproduce

  1. Self extract Google Chrome Portable 64-bit.
  2. Click + Browser in the chat:
  3. Browser isn’t detected:

Expected Behavior

If browser isn’t detected, it should let me enter a manual path, just like Cursor lets me do it for Python.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.46 (user setup)
VSCode Version: 1.99.3
Commit: b9e5948c1ad20443a5cecba6b84a3c9b99d62580
Date: 2025-10-14T01:21:46.830Z
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.26200

Additional Information

This is a major issue, please fix, all you need is to let me supply a path.

What do you think, @deanrie?

Does this stop you from using Cursor

Yes - Cursor is unusable

1 Like

Hey, thanks for the report. You’re right: the Browser feature doesn’t currently support portable browsers or allow setting a manual path.

The Browser feature is still under active development, and this limitation is planned to be addressed. A manual path option would be useful for portable installations.

Workaround: install the standard version of Chrome alongside the portable one, Cursor should detect it automatically.

Let me know if this workaround helps!

That’s not exactly a workaround, but more like avoiding the issue to begin with.
If you’re willing to let me define a path manually, I’ll be glad to do it in CFG/INI/JSON/etc. to test that it works.

v2.0 has come out and added Chrome Executable Path, but it seems to be ignored.
Why is that, @deanrie?

Did anyone manage to get it to work, especially with Chrome Portable?

Why does something so simple go wrong, @deanrie?

I think I can see the same problem. When I specify Chrome Canary, Cursor has problems with accessing that binary. The bundled Chrome or the built-in web browser work fine though.

Version:

Version: 2.0.43
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: Darwin arm64 24.6.0

Well, at least you get Ready state instead of Chrome not found. Could it fail in both Mac and Windows with different reasons?

If you already have this option, why doesn’t it work, @deanrie?