@Browser stuck on "Waiting for Approval..." with no way to continue

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor stopped launching a browser for @Browswer and now just get sutck on “Navigate to https:…” and “Waiting For Approval”

Steps to Reproduce

Enter the following in the Agent Window: Test @Helium
with @Browser. Username is 324234234 Password is asdfasdfasdf.
Navigate to Water → Existing System

Expected Behavior

Chrome would usually open and the testing would continue

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.44 (Universal)
VSCode Version: 1.99.3
Commit: 9d178a4■■■89981b62546448bb32920a8219a5d0
Date: 2025-10-10T15:43:37.500Z
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

For AI issues: which model did you use?

Auto

Additional Information

It started after I enabled “Cursor Browser” in Cursor Settings → Beta. Now behaviour is the same with the setting On or Off

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I am trying to access the new At Browser feature, but the agent keeps responding as though it can’t see anything and looks through the codebase instead, as though this is not a feature that is built yet. I do see the At Browser button, but it doesn’t seem to work every time that I use it. That is, the agent responds with that it is not a functionality. It has to see the actual browser output.

in Cursor settings I see: Browser Automation
Ready (Chrome detected)

Steps to Reproduce

@Browser and ask agent question. using Auto for Sonnet 4.5. Chrome standard installed

Expected Behavior

Agent should see browser outout

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.44 (Universal)
VSCode Version: 1.99.3
Commit: 9d178a4■■■89981b62546448bb32920a8219a5d0
Date: 2025-10-10T15:43:37.500Z
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.1.0

For AI issues: which model did you use?

Sonnet 4.5, Auto

Does this stop you from using Cursor

No - Cursor works, but with this issue

Oh so it’s not just me, It can’t navigate and can’t see even it even If I open the url myself.

Here is the error: {“error”:“MCP error -32603: No browser tabs have registered with the MCP server. The iframe may have failed to inject the automation script (likely due to cross-origin restrictions).”}

You’re one step ahead of me. I don’t even see the browser tab appear in the center panel.

Do you also have to register an MCP in order to get this function to work? I didn’t see that in the documentation.

I think it’s because I’m using the agent window. If you don’t use Agent Window you won’t see the browser at all.

Edit: You only need to make sure “Browser Automation” is enabled in “Tools & MCP” settings.

I see it in agent window (as an @ option) it just doesnt do anything. And yes Browser Automation is enabled for me

I reinstalled Cursor instead of updating it, and now the feature is working as expected. That is, I downloaded the package again and reinstalled it to the Applications folder in Mac OS.

1 Like

Just tried on windows and reinstalling directly does not fix it, however, uninstalling/reinstalling did fix the issue. Thank you!

1 Like

Hey @agreylingmezzanine, sorry you ran into this frustrating issue with the Browser feature!

It looks like @drjjw and @webdo found a workaround in this thread - uninstalling and reinstalling Cursor (not just updating) seems to fix it. They confirmed it worked on both macOS and Windows.

That said, this definitely shouldn’t be the experience when enabling a beta feature. We’ll raise this with the team to make the setup smoother so you don’t have to go through a full reinstall just to get this working.

Let us know if the reinstall helps!