Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
- The setting that lets us disable this has been removed.
- We can select 3 different modes - if we deliberately select modes which are not enabled, cursor ignores the mode we chose and uses the one it finds which works - which again thwarts us form disabling this.
Please do NOT FORCE TOOLS ON US - unwanted tools bloat our context and deprive us of using vastly superior 3rd party tools which your unwanted inbuilt ones override.
Response 1
[1 tool called]
Based on my system prompt, here is the complete browser automation tool documentation that’s loaded in my context:
Browser Tools Section
The section is titled <browser_tools> and contains approximately 1,850 tokens of instructions. Here’s the complete content:
Available Tools:
mcp_cursor-ide-browser_browser_navigatemcp_cursor-ide-browser_browser_snapshotmcp_cursor-ide-browser_browser_clickmcp_cursor-ide-browser_browser_typemcp_cursor-ide-browser_browser_hovermcp_cursor-ide-browser_browser_select_optionmcp_cursor-ide-browser_browser_press_keymcp_cursor-ide-browser_browser_wait_formcp_cursor-ide-browser_browser_navigate_backmcp_cursor-ide-browser_browser_resizemcp_cursor-ide-browser_browser_console_messagesmcp_cursor-ide-browser_browser_network_requestsmcp_cursor-ide-browser_browser_take_screenshot
Instructions include:
-
Purpose: Navigate, read, and interact with web pages as a user would, providing comprehensive view of dynamic content and JavaScript-rendered pages
-
Parallel Tool Calls: Capability to call multiple tools simultaneously when operations are independent (e.g., taking screenshots of multiple pages, navigating to multiple URLs)
-
Suggested Testing Flow:
- Navigate to page
- Snapshot to get elements
- Interact with elements and observe results
- Re-snapshot when changes expected
- Use screenshot tool for visual inspection, then read the image
- Repeat for each feature, prioritizing key cases
-
Avoid Behaviors:
- Don’t start local web server unless prompted
- Don’t guess server ports (look through codebase or ask user)
- Don’t use shell to interact with browser
Token Waste Analysis:
Given that you don’t want this tool, this represents approximately 1,850 tokens (roughly 1.8% of a typical context window, or 0.185% of your 1M token budget) being consumed on every single message with instructions for a feature you’re not using.
Would you like help documenting this to provide feedback to Cursor about making browser tools opt-in rather than always-loaded?
Steps to Reproduce
disable the browser - no way way anymore - see before and now screenshots here:
Expected Behavior
option to disable this
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.1.46 (system setup)
VSCode Version: 1.105.1
Commit: ab326d0767c02fb9847b342c43ea58275c4b1680
Date: 2025-12-02T03:59:29.283Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100
Additional Information
it would be nice if you got some QA into your deployment pipeline - you should not be using your userbase as bugfinders!
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor
