Cursor Browser Agent doesn't work

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The Browser Agent doesn’t seem to work at all. Sometimes the Browser tool says its “Ready (Chrome detected)” but more often it just says “Unable to check status”. In either case the agent does not work.

Steps to Reproduce

I have it enabled in the settings and I’m in Agent mode. I prompt something like “navigate to google.com” and it just hangs.

Expected Behavior

The browser agent should be able to use the browser in any way.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.44 (system setup)
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: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey, thanks for the report. This is a known issue and we’re already looking into it.

Quick question: Are you using Agent mode in the standard editor window, or are you clicking “Open in Agent Window”? Several users noted that Browser tools work in the main editor but not in the separate Agent Window.

Could you try running the Browser Agent in the standard editor (not in the Agent Window) and let me know if that makes a difference?

TBH I’m not 100% sure about Agent window vs Editor window - I’ve just been using whatever the default experience is when cursor opens.

I found an option at the top to “Open Editor in New Window” so when I do that and try to use browser agent I get the same behavior and these errors.

Cursor in safe mode in a new empty folder

Thanks for the info, that’s very helpful.

I just arrived here investigating the same issue and can confirm that I was getting it in agent mode but not in standard. When I check the settings and Tools & MCP in the standard mode I can see Browser Automation Ready(Chrome detected) but when I tried the same setting in the agent mode I saw “unable to check status” rather than “Ready (Chrome Detected)” Switching back to the standard editor I’m able to use the browser automation again. Hope that helps narrow down the issue a bit. I’m quite new to the product but I believe I was opening an agent window.