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.
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.
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.