Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
This is a long, long standing issue now. Its been two months or more, probably more based on the last time I can remember the docs feature actually working. I relied HEAVILY on the @Docs feature, because without it, the agent is often just guessing or assuming, which is evident in its responses. Even if the agent/model are able to search the web, the results are just not as good as when you can use @Docs.
I have just moved to a brand new Macbook M2 Pro, clean slate, very light weight setup, brand new fresh clean install of Cursor. The @Docs feature still does not work in Cursor. The agents, even though they sometimes seem to be referencing the docs, at least they say they are, they are NOT, and the results of their work without docs is often very pitiful, riddled with guesses, assumption, and blatant fabrication. This was never the case, when @Docs actually worked.
When @Docs worked, you could clearly see the sections of the indexed docs that the model referenced, and the results were phenomenal. The models would know exactly how to use third party frameworks, and could solve complex problems quickly and very effectively. Right now, I’m getting a ton of guesswork and fabrication of “knowledge” that is simply false, and the agent (even after many web searches) cannot build correct code. In this case, I am trying to build a Better Auth server.
I’m sharing two request ids. One with Composer 1, another with Sonnet 4.5. Neither model, seems capable of actually referencing the docs I have indexed for Better Auth. Composer 1 initially just gave me false information (I had read the docs myself, so I knew it was fabricating) about Better Auth’s capabilities.
This is just unacceptable. The @Docs feature and doc indexing is one of the reasons I signed up for my Ultra plan in the first place. I started using this very early on, back around April time frame this year, and the improvement in the quality and correctness of code implemented by the models with @Docs was SO FAR BEYOND normal usage, that @Docs usually found its way into nearly all of my prompts.
Now the models cannot use the @Docs feature, and the quality of the code produced is pitiful in comparison, the models are constantly guessing and assuming. They will guess and assume even after extensive web searches, so web search is NOT a viable alternative to @Docs.
I’ve been asking you guys what the deal is with @Docs for months now. I really would like to know: Is this a feature you guys are going to fix? OR are you just going to ignore it and let it die? There is no alternative for @Docs, as far as I have ever been able to find. This was one of the SINGLE MOST POWERFUL features you guys had, and you killed it months ago and seem fit to let it die.
I really, heavily, persistently RELIED on this feature, and I am really starting to have a hard time using Cursor without it. My current use case, the darn models just cannot seem to fully understand Better Auth and they are just giving me results that seem to come from rudimentary understanding from their latest trainings. Not the deep, ultra rich and EXACT knowledge they used to have when @Docs worked.
Sonnet 4.5
Composer 1
The ridiculousness here, is Composer 1 seemed to be able to include a reference to @Better Auth Docs in its response, figured the docs were “indexed elsewhere”, but couldn’t access them!
I do wonder if this is part of what appears to be a deeper issue with MCP support in Cursor in general. I’ve pushed the models to use @Docs hard in the past, and they will usually eventually try to connect to it as an MCP server. I assume that is, in fact, how its implemented, that it is basically an MCP and exposes tools? Is there a bug in how the @Docs context and tooling is exposed that was introduced back at the end of August or beginning of September?
I also wonder if there may be some Cursor Account level limitation here. This issue seems to FOLLOW ME AROUND, from one install to the next, even the most pristine install possible. Is there something misconfigured, corrupted, or otherwise broken with my Cursor account, that is preventing this feature from working?
I really need this feature. Second only to the terminal issues that plagued Cursor for several months before 1.7.35 was released, lack of @Docs is the single most impactful bug that affects my work right now with Cursor. It has a huge impact on the quality and correctness of the models, in terms of implemented code, but also just understanding how any given third party library, framework, CLI, or other tooling works, which then leads into planning, software design and architecture, etc.
Steps to Reproduce
Index one or more third party library docs sites (in my case, Better Auth).
Ask the model to use the docs via the @Docs command palette.
Weep at the lack of actual reference via @Docs, and subsequent misinformation, obfuscation, guesswork, assumption, and fabrication of false knowledge, bad implementations, etc.
Expected Behavior
@Docs should work, the way it did before, providing deep, rich insight into how third party libraries or common frameworks work, without the need for web searches, guesswork, assumption or fabrication by the models.
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.0.64
VSCode Version: 1.99.3
Commit: 25412918da7e74b2686b25d62da1f01cfcd27680
Date: 2025-11-06T04:35:14.424Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.0.0
For AI issues: which model did you use?
Composer 1
Sonnet 4.5
For AI issues: add Request ID with privacy disabled
fc110e51-e094-49dc-9de6-0c6d3502fd63 (Composer 1)
42296efa-909e-43b2-af16-0a1608c0f08b (Sonnet 4.5)
Does this stop you from using Cursor
No - Cursor works, but with this issue
is monstruos, LOL.