“Agents are good enough to get docs using browser”
Maybe. However, does that justify taking the feature away from your paying customers? The Docs were one of the only WORKING ways to steer the agent in the direction where I want it to go.
The agents may be able to browse the web, but.. it doesn’t work as good as you say it’s working. You cannot trust them to do exactly what you want them to do, and at least with Docs they read the right page. It is also a good way to craft actual docs from some online instructions, such as cursor own webpage manuals.
The agents surfing themselves doesn’t only work worse, but it also costs more tokens. So, please give the docs back.
Hey, thanks for laying out the reasoning, both about steering to the right pages and about token cost. Those are fair points, and the team has seen them.
Docs was removed intentionally in 3.14.2 after a careful decision. There’s a main thread with the discussion and the team’s reasoning: Cursor 3.14.2 Sunsetting @Docs!?!. I’d suggest adding your voice there so everything stays in one place.
For now, the closest workflow replacements are:
Paste the exact URLs for the docs you want directly into the prompt. The agent will read those pages specifically instead of choosing on its own.
Put the instructions or guidelines you need into a rule or skill so they apply automatically every time (rules, skills).
Let me know if this approach doesn’t cover your use case.
@samuleinen, @deanrie is correct that my thread was the first discussion of the @Docs removal. The problem is that Cursor keeps directing everyone there while refusing to answer the questions being asked.
For repeated use of the same documentation corpus, does the replacement workflow consume more tokens than @Docs did?
@Docs indexed documentation once. The replacement makes the agent repeatedly search, fetch, read, and reconstruct that context. Cursor has said token usage “wasn’t a factor” in the decision, but that does not answer whether the replacement actually burns more tokens.
There is also an unanswered backward-compatibility question: What happened to everyone’s saved @Docs URLs and curated documentation data? Can users recover or export it?
Consolidating discussion into one thread is reasonable. Redirecting everyone to that thread while Cursor refuses to answer its central technical questions is not.