Still broken on 3.18.9 (Linux Ubuntu 24.04 x64, Glass). Adding a local-agent repro that matches this thread’s No browser view available and also explains the 30s “re-register” failure the agent sees.
Error the agent gets
Server not found: cursor-ide-browser (MCP provider did not re-register within 30000ms)
GetDynamicTools can still list cursor-ide-browser as namespaceStatus: ready (stale catalog). The next CallDynamicTool then waits 30s and dies. Retrying the same call burns another 30s.
Logs (every new Glass workbench today)
~/.config/Cursor/logs/20260902T083539/window1_wb*/…/1-Cursor IDE Browser Automation.log
On all 11 workbenches (wb0–wb10):
Cursor Browser Automation extension activated
Using Browser MCP provider
injectBrowserUIScript called
[ERROR] Failed to inject browser UI script:: No browser view available
at …/workbench.glass.main.js
On wb10 (created 09:52 local, same second as a move_agent_to_root abort):
Browser Automation MCP Provider disposed
After that dispose, browser MCP stays dead in the chat. Reproduced again at 10:08 by calling browser_tabs — same 30s re-register timeout, no new workbench.
Why it happens here
- Glass + many workbenches in one Cursor window
move_agent_to_root(even when the destination folder is already in the multi-root workspace) spawns a new workbench- Extension activates before any Simple Browser view exists → inject fails once → provider disposed → no retry
- Same race this thread already described; Reload Window is not a fix
Expected
- If no browser view yet: keep the provider alive and inject when the first tab/view appears
- Do not dispose after a single failed inject
- Do not advertise tools as
readyafter dispose - Fail the tool in <1s, not after a 30s re-register wait
move_agent_to_rootto an already-open multi-root folder must be a no-op (related: #169527)
Environment
- Cursor 3.18.9 (
2ba48ff), stable, Linux x64, Glass - Local Agent, not Cloud / not Remote-SSH
- Multi-root
.code-workspace(11 folders)
Related closed thread: Browser MCP Tools Not Available
Related move_agent_to_root: Move_agent_to_root aborts the in-flight turn and never resumes (“Switching workspace root”, then silence)