Referencing @docs does not work for all cases

Discussion
1

Hello everyone,

I’m experiencing an issue when using the @docs command in chat. Some URLs work perfectly fine, but others cause the request to fail.

Here’s a screenshot of the error:

image
image946×630 35.9 KB

I’ve already tried disabling HTTP2 using the setting:
cursor.general.disableHttp2: true

Unfortunately, the problem persists.

Maybe there is an issue with how the documents are being crawled or indexed. Or, it could be a server-side protection mechanism that is blocking scraping attempts. However, when I give the URL directly to any LLM, they are able to access and summarize the content successfully.

Has anyone else encountered this problem or found a workaround? Any suggestions would be greatly appreciated!

Thanks for your help.

2

Hey, is this happening only with this documentation?

3

Hello,
Yes, when I add this Cursor documentation page instead it’s working.

image
image890×1244 95.9 KB

4

Probably the issue is with the documentation itself. What if you delete it and add it again?

5

Tried many many times, but same outcome.
I don’t think it’s related to the documentation itself because when I put the link in the chat and ask it to summarize, it’s able to get it and summarize it.