Opus 4.5 is continuing to tell me it does not have the tool to use the browser tab even though for the last 2 weeks it has had no issue doing so.
Steps to Reproduce
Making sure in the prompt options you have “connected to browser tab” turned on and tell it to use the browser tab to read the docs on the page you have open. (make sure you have a page open you want it to read also)
Expected Behavior
All of the llms have had no issue doing this. They go to the tab and read the snapshot of the page it had been working flawlessly up until today.
I tried both in agent mode and edit mode and yeah I tried both the external browser and internal browser tab. It just continues to tell me it does not have that tool and as the image shows it listed the tools it says it has access to and no browser tool in the list. I used the exact dame model for 2 weeks straight and used that tool countless times, then switched agents to gpt 5.1 codex max high for one day, codex broke the hell out of an app 8 am 5 months into and about to release so I reverted back to the first prompt using codex and switched back to opus 4.5 agent and this is the state it’s in currently.
# Browser tool usage
_Exported on 1/13/2026 at 20:19:30 PST from Cursor (2.3.35)_
---
**User**
Can you use the @Browser tool?
---
**Cursor**
I can use the Browser tool! I have access to two browser-related MCP servers:
1. **cursor-browser-extension** - Allows me to navigate the web and interact with pages
2. **cursor-ide-browser** - Similar browser capabilities for web navigation and interaction
Let me check what specific capabilities are available:
Yes, I can use the Browser tool! I have access to browser capabilities through the MCP servers. These allow me to:
- Navigate to web pages
- Interact with page elements
- Test frontend code and web applications
- Use JavaScript to inspect elements (like `getBoundingClientRect()`, `innerHeight`, `innerWidth`)
Based on your workspace, I see you're working on a Next.js mortgage portfolio website with multiple loan product pages. Would you like me to:
1. **Test the application** by opening it in the browser?
2. **Navigate to specific pages** to check functionality?
3. **Inspect or interact with elements** on your site?
4. **Test something specific** you're working on?
What would you like me to do with the Browser tool?
---
**User**
Go to example.com
---
**Cursor**
I apologize, but while I can see that there are browser MCP servers configured (`cursor-browser-extension` and `cursor-ide-browser`), I don't currently have access to the actual browser navigation tools from those servers in my available function list.
The MCP servers are mentioned in the system instructions, but the specific browser tools (like navigate, click, type, etc.) aren't showing up in my available tools at the moment.
This could mean:
1. The browser extension needs to be activated or connected
2. The tools from the MCP servers aren't currently exposed to me
3. There might be a configuration issue
Could you check if:
- The Cursor browser extension is installed and running?
- The MCP servers are properly connected in your Cursor settings?
Alternatively, if you're trying to test your Next.js application locally, I could help you:
- Start the development server with `bun dev`
- Open a local HTML file for testing
- Use other available tools to help with your development
What would you like me to try instead?
