Web browsing and document context not working

Whenever I try to use @web or @docs the LLM (I’ve tried both claude-3.5-sonnet and gpt-4o) I’m told that documentation nor browsing are capabilities. I’m running version 0.45.10 and have premium.

Hey, does this also happen in a new session?

Hey @deanrie yes this happens in new sessions - I’ve tried with multiple fresh instances and also tried restarting both my Mac and Cursor.

update on this - i think this may be due to a VPN. for the official documentation (and the manually indexed) is the text stored locally or remotely? may explain the issues.


update on the update: I’ve tried two different VPNs as well as no VPN, but I still get this back from the LLM

ah I see what’s happening! @web and @docs aren’t actually tools for the LLM - they just provide context directly to it. Could you try opening a fresh composer (Cmd/Ctrl + K) and see if that works? That should give you a clean slate to work with

if that doesn’t help, let me know and we can dig deeper into what might be going on


well this is confusing/misleading then? whenever I ask it to browse the web (and I’ve tried many times since opening this thread) it just says it can’t, whether or not I include the @web tag.

so basically @docs and @web just fail about 95% of the time for me (I’ve seen both work…or at least lead me to think they worked a handful of times).

I’ve updated Cursor every time its asked me to. I have a fairly vanilla setup on a typcal MacBook. I’ve ruled out (and stopped using) a VPN when working in Cursor…

Not sure what else to try?

Both @docs and @web should work every time, do you have a screenshot of this?

In v0.46, the agent now has the ability to read docs and the web on its own, but manually triggering it should work every time!

Its recurring. web searches crash: 9038580f-9956-4cdd-9e85-c1269c284828 with User aborted request (havent touched Cursor).
Tool call ended before result was received error. also on search

Using 0.46.4. (network is fine)

Looks like the web crawler is seeing some delays, will flag to the team, but will likely resolve on it’s own over time!