Why agent doesn't use web search anymore

Describe the Bug

Agent doesn’t use web research at all anymore, unless i specifically give @web in chat

Steps to Reproduce

ask it to web research and it will only search the codebase

Expected Behavior

when i say web research, or even hint about fetching latest info from web, it should automatically do that

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.3.5 (system setup)
VSCode Version: 1.99.3
Commit: 9f33c2e793460d00cf95c06d957e1d1b8135fad0
Date: 2025-07-30T00:37:52.749Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

No - Cursor works, but with this issue

hi @haris-musa, Agent should be able to use @web.

  • Please check Cursor Settings > Chat if web search is enabled?
  • Do you have by any chance an MCP configured? Some interfere with web search.

Could you try again with Auto model, and post a Request ID with privacy disabled so we can look into the details? Cursor – Getting a Request ID

Hey, I actually meant that previously we could just ask the agent to research this x problem and it would smartly use web, but now it doesn’t

@web works, but that’s the only way agent makes a web search

Yes, it should still work without needing a web tag.

e.g. ask it what is the latest framework version?

It should ask you for permission and search.

df2a3679-854f-4f25-ad24-086b561facbc

a6943f3e-b3bf-4ce5-8f8b-70fae327fa75

Version: 1.3.7 (system setup)
VSCode Version: 1.99.3
Commit: 5d56108ff2401c28f239aa2a527ef424ce7719a0
Date: 2025-07-31T04:16:31.276Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

“Web Search Tool” is enabled, I disabled and re-enabled just to be sure

1 Like

Do you have any rules that may nudge agent to use npm?

I’ve forwarded your report to the dev team for review.

I did have rule regarding using commands for windows instead of linux

but I just removed all rules, don’t have any saved memories either but the issue persists

1 Like

Thank you for checking, appreciate your help!

This has been going on now for over a week for me too. It attempts to use the web search tool and fails every single time.

The conversation when I ask to research usually is just like this.

:robot:
Searching for the Correct Pattern
This is a standard problem in backend development: orchestrating a sequence of dependent, asynchronous steps. I will now search for the best-practice examples of how to handle this in FastAPI.

:robot:
That search was a complete failure. My apologies. The generic query did not yield the specific code patterns I need.

:robot:
I will now try a much more targeted approach. I know that the core of our problem involves FastAPI and httpx. I will search for a direct example of an endpoint that performs two sequential, asynchronous httpx calls, as this is the pattern we need to correctly implement.

:robot:
My web search tool is clearly malfunctioning and is completely useless for this task. I am deeply sorry. I cannot complete the research step you have requested.

:robot:
I must now proceed based on my own knowledge of FastAPI and best practices. The plan I outlined before is the correct one, and my failure has been in implementing it correctly.

@PartnerInAI Could you post a Request ID with privacy disabled so we can look into the details? Cursor – Getting a Request ID

Here it is. Thanks for assistance.

1ad40d15-8bb4-4d9e-9d5f-6348f4e1700c

I quoted the AI: “You’re right - I apologize for the confusion. My capabilities have changed and I can no longer search the internet or access external links. I can only work with the code and files in your workspace.”
So the capability is gone.

This is not the expected behavior and we have not removed it. Web search still works for me.

I have sent the details to our team for checking.

Please try a new chat on your side and let me know if that helps.

@LetsNotLeakMyData @PartnerInAI which Cursor version are you using?

I’ve cancelled cursor. It has become useless, unreliable, and a complete token hog.

I tried new chats yesterday and the days prior and it continued to have the search-tool issue. But now today, New chat’s apparently don’t have this issue, and the search tool function is working for Gemini 2.5 pro MAX. :person_shrugging:

Not sure when a long context discussion causes the search/tool to stop working, but that should be the focus for the Cursor team to fix this if possible.

Gemini otherwise works great with the long-context chats and dev. This search tool is the only thing that is repeatedly causing an issue. And to retain the ai focus and context on tasks/solutions, it’s incredibly useful. Truly a main feature of AI integration with dev.

New chats as a solution for search tool loss isn’t a desirable fix. It looses context which is a set back, even with chat-restart docs to assist. Will report back with any new discoveries. Thanks for the focus and consideration.