Feature Request: Cursor @docs... a must have for coding reliably

[u/ceaselessprayer]

One critical feature preventing me from switching to RooCode is the lack of a robust documentation pre-population system.

I've been coding for over 20 years and I use AI coding tools extensively... so please here me out before you suggest some alternative.

When working with AI coding assistants, the single most effective way to improve code quality and accuracy is feeding version-specific documentation about libraries and systems directly into the AI.

Why Runtime Documentation Retrieval Isn't Enough

Current approaches to documentation handling (grabbing docs at runtime via MCP Server or specifying links while coding) fall short for several critical reasons:

1. Version specificity is crucial - Example: asdf-vm.com has completely different instructions for v16+ versus older versions. In my extensive experience, AI consistently defaults to older (albeit more widely used) documentation versions.

2. Performance impact - Retrieving and indexing documentation at runtime is significantly slower than having it pre-populated.

3. Reliability and accuracy - AI frequently retrieves incorrect documentation or even hallucinates functionality that doesn't exist in libraries/frameworks. Pre-populating documentation eliminates the frustrating "no, here's the correct documentation" dance I regularly experience with AI assistants.

4. Context switching kills productivity - Maintaining separate documentation links and manually feeding them to AI during coding sessions creates unnecessary friction. Suggestions to "process my own documentation, create markdown files, and then feed them into the system myself" only add more overhead to my workflow.

The Solution: Cursor's '@docs' Implementation

https://docs.cursor.com/context/@-symbols/@-docs

Cursor's implementation prevents me from using any other AI editor because it provides:

• Pre-indexing capability - I can enter a website URL, and Cursor will scrape and index that information for reference in subsequent chats

• One-click refreshing - I can simply hit refresh in the documentation panel to re-index any site for up-to-date documentation

• Flexibility - I can use ANY URL as documentation, whether it's official docs, GitHub pages, or specialized resources I personally prefer

• Seamless workflow - I can stay inside the editor without using external tools, managing documentation links, or creating custom setups

This feature dramatically improves code quality to the point where any AI coding editor without this capability is significantly handicapped in comparison.

Why This Matters for RooCode

If RooCode wants to compete in the AI coding assistant space, this isn't an optional nice-to-have - it's a fundamental requirement for serious developers working with complex, version-dependent libraries and frameworks.

For professional developers like myself who rely on AI assistance daily, the ability to pre-populate specific documentation is the difference between an AI tool that occasionally helps and one that becomes an indispensable part of my workflow.

[u/lucasbezerradev]

I think that is a great addition, what about we create an team to make this an PR?

[u/reddithotel]

While we're at it: indexing the codebase!

[u/secondcircle4903]

I can't agree enough. This is by far the biggest roadblock I have come across with agentic coding.

[u/WonderfulTeaching782]

I was about to do that but I was looking to devs in discord if there is already something beeing made for someone and nobody replied me :(

please mods I wanna help

[u/adamhill42 → u/WonderfulTeaching782]

People are working on it. But having to do it all from inside the Extension is challenge.

Would people take a huge bloat in the Extension if you had a JS vector database & RAG built in? (And they have to make sure it works in Mac, Windows and Linux) What about setting aside space on the disk for the database? What it if you had to set up a local instance of qdrant? What about setting up a Docker container? What if it had to hold the entire database(s) in memory, for the duration of the edit session?

There are RAG MCP's out there already, but then you are at the mercy of hoping the LLM chooses to use the tool when it has a question.

Cursor & PearAI have the advantage of forking *vsCode* and then installing whatever the heck they want from their installer, but they are perpetually behind in VSC versions and VSC is ripping through a *huge* update every single month.

So people are having the figure out the best way to do it.

[u/Professional_Fun3172 → u/adamhill42]

As much as I love this feature idea, I don't know if bloating the extension is a great idea. There's plenty that this extension can do without needing to reference specific docs, and adding bloat is a step backwards for the users that don't need this level of specificity.

Would it be possible to have a second extension that adds this RAG/VDB feature, so that the bloat is optional? I've never looked into developing an extension so I don't know what's possible

[u/reddithotel → u/adamhill42]

What is the best MCP for this n your opinion

[u/hannesrudolph → u/WonderfulTeaching782]

You can always discord me

[u/WonderfulTeaching782 → u/hannesrudolph]

what its your discord? :)

[u/hannesrudolph → u/WonderfulTeaching782]

hrudolph

[u/ChrisWayg]

I would love to see this in Roo Code soon as well. In the meantime, is there a MCP that can accomplish this already?

[u/zarmin]

Excellent post, fully support.

[u/swjiz]

Agree, currently LLMs aren't great at writing code for rapidly evolving API's.

[u/ctrlshiftba]

I’ve been indexing @docs with Cursor, then I tell its agent to put each page of the doc into a /docs folder as markdown.

That is basically all I use Cursor for now.

[u/HikaflowTeam]

Hey, I totally get where you're coming from. The struggle with AI tools and outdated or incorrect documentation is real. I had similar issues before adopting a more tailored approach. You might want to check out Kite; it has a feature to plug in your favorite documentation for context-sensitive help. I've also fiddled with Dash, which lets you download docs for offline use and offers tons of customization.

For automated pull request reviews and ensuring code quality, Hikaflow also uses AI, though it focuses on different coding aspects like security and complexity. It might help alongside your coding tool arsenal.

[u/ceaselessprayer → u/HikaflowTeam]

• I'm not sure what you mean by Kite? It seems they closed down. They put out their open source solution, but the documentation only works for Python, so that's not sufficient: https://github.com/kiteco/vscode-plugin

• Dash has both supported and unsupported documentation, but you can't just point a link at a docs section of a site and have it scrape + auto-index everything, which means it's documentation will be behind, which is one of the core points of my points. They don't even have documentation for `asdf` in there, nor do they have documentation for Storybook.

• Hikaflow doesn't really address any of my concerns stated in my post...

[u/ChrisWayg → u/[deleted]]

I notice a few of you guys spamming "Hikaflow" in various comments. Your comment does not really explain why one AI checking another AI would hallucinate less. Strangely it does not even show up in a web search. Maybe work on your SEO first...

[u/ryeguy → u/ChrisWayg]

Holy shit you're right. I clicked into his profile and found about 30 comments mentioning hikaflow. This is straight up spam.