Browser inside IDE (not remote controlled Chrome) is broken

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The built-in browser feature in the Agents works differently the Chrome and breaks usage of our app.

We use Google Identity Platform and both sign in with Google and sign in with email are broken.

Sign in with Google required me to sign in to my Google account in the browser, but then since Google Identity Platform opens a new tab to do the redirect to login via Google and then closes that tab returning the user to the app, it failed (since Cursor doesn’t seem to handle the browser having multiple tabs).

Sign in with email failed due to some weird Content Security Policy error that I don’t see in Chrome:
Refused to connect to ‘https://identitytoolkit.googleapis.com/v1/accounts:createAuthUri?key=blah’ because it violates the following Content Security Policy directive: “connect-src http://localhost:* ‘self’”.

window.fetch @ fetcher.js?v=a2a83240:66
(anonymous) @ chunk-WLCO2TG7.js?v=a2a83240:1080
await in (anonymous)
_performFetchWithErrorHandling @ chunk-WLCO2TG7.js?v=a2a83240:1089
_performApiRequest @ chunk-WLCO2TG7.js?v=a2a83240:1049
createAuthUri @ chunk-WLCO2TG7.js?v=a2a83240:4853
fetchSignInMethodsForEmail @ chunk-WLCO2TG7.js?v=a2a83240:4861
fetchSignInMethodsForEmail @ firebaseui.js?v=a2a83240:1819
l.I @ firebaseui.js?v=a2a83240:9373
$l @ firebaseui.js?v=a2a83240:10218
(anonymous) @ firebaseui.js?v=a2a83240:11591
(anonymous) @ firebaseui.js?v=a2a83240:9765
(anonymous) @ firebaseui.js?v=a2a83240:9106
ye @ firebaseui.js?v=a2a83240:4350
xe @ firebaseui.js?v=a2a83240:4325
dj @ firebaseui.js?v=a2a83240:8658
cj.h @ firebaseui.js?v=a2a83240:8651
ve @ firebaseui.js?v=a2a83240:4241
re @ firebaseui.js?v=a2a83240:4280
b @ firebaseui.js?v=a2a83240:4194

Steps to Reproduce

Try to login to any application with Google Identity Platform AFAIK

Expected Behavior

The login should work

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.38
VSCode Version: 1.99.3
Commit: 3fa438a81d579067162dd8767025b788454e6f90
Date: 2025-10-29T20:45:40.883Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.0.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. This is a known issue with the new Browser Tab feature introduced in Cursor 2.0. Several users are seeing similar problems in the built‑in browser.

The team is actively improving Browser Tab, and we’ve shipped fixes for some issues in recent updates. I’ll pass this to the team since it’s blocking authentication flows.

Also, please update to the latest version (currently 2.0.44) and see if the recent fixes help.