When I ask the AI to access the browser tab, it responds that it is unable to do so, specifically:
“I am unable to interact with the browser tab directly from here, so I cannot navigate to that page for you. If you need me to check something specific within that tab, you can share a screenshot or paste the relevant HTML/text here.”
In version 2.4.30 of Cursor, the AI was able to access it, so I assume there has been a regression.
(Attached is a screenshot of the browser tab.)
Browser tab configuration: Tools/Browser automation/Browser tab.
Steps to Reproduce
Ask Ai to navigate and interact in the browser tab
Expected Behavior
I expected that it could interact and navigate the browser tab to help me with web development.
Hey, this is a known issue: the Browser Tab sometimes becomes unavailable to the agent. We had a similar regression starting in 2.3.18 that got fixed, but it looks like it’s broken again in 2.4.31.
A couple things to help diagnose:
Try turning Browser Automation off and back on in Settings > Tools & MCP, then fully restart Cursor.
If that doesn’t help, can you share the Request ID from the chat where the agent refused to use the browser? (top right of the chat > Copy Request ID)
As a workaround until this is fixed, you can manually connect the Microsoft Playwright MCP via the MCP config. It will give control over an external browser.
I’ve passed this to the team. Let me know if the restart helped.
I installed the MCP server you recommended, but even so, the AI cannot access the browser tab. The error message given by the AI is that it cannot access the MCP tools for agents.
Request ID: 2fb2b074-b37a-4682-b790-fa52fcce1d7a
I updated Cursor to the latest version available before running the tests:
Version: 2.4.32 (user setup)
VSCode Version: 1.105.1
Commit: dac77182205e080f83e43f13ee42d822740a6e10
Date: 2026-02-09T05:01:38.814Z
Build Type: Stable
Release Track: Early Access
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200
Root Cause: This issue arises from a regression in the functionality of the Browser Automation feature following the update to version 2.4.31, potentially due to conflicts in the underlying tools connecting the AI to the browser tab.
Suggested Fix:
Disable and re-enable the Browser Automation feature: Go to Settings > Tools & MCP > Browser Automation and toggle it off, then back on.
Fully restart Cursor to ensure settings take effect.
Test the functionality again by asking the AI to navigate in the browser tab after the restart.
If the issue persists, check for any updated patches or releases beyond version 2.4.32, as the team may have addressed the bug.
If still unresolved, gather the Request ID for the incident (already provided: 2fb2b074-b37a-4682-b790-fa52fcce1d7a) and contact support for more detailed investigation.
If toggling doesn’t fix it, check whether the browser tab is actually running in Cursor’s embedded browser. The AI can only interact with tabs opened through Tools > Browser Automation > Browser Tab — external browsers or even VSCode’s simple browser won’t work. Also, version 2.4.31 introduced changes to MCP (Model Context Protocol) integration that might be interfering. I’ve seen similar regressions get patched within a day or two in the Early Access track, so you might want to check their changelog or Discord for acknowledgment. In the meantime, if you’re stuck on urgent dev work, rolling back to 2.4.30 is an option — just download the specific version from their releases page rather than using the auto-updater.
— Delimit · dev problems deserve fast answers · AI-suggested, corrections welcome
Now I’ve finally managed to get the AI to access the tab browser. I turned off the MCP server, turned off browser automation, reactivated it on Tab Browser, and restarted Cursor: now it works!
