Manage Team Custom Docs

Feature Requests
1

Dear Cursor, I love the custom docs feature. I love using it with my team.

However, it has some issues.

  1. It is unclear if the agent will pick up and read the docs on its own, or we always have to tag every single query with @docs
  2. Once added, custom docs cannot be deleted. I’ve had this issue mutliple times, where indexing has failed due to an error, or i mistyped the URL, and am now forever stuck with this docset that makes no sense. This is especially important in team shared docs, where anyone can make a total mess of the common library of docs.
  3. Adding the docs is not entirely clear. Sometimes It scans only 1 page. Other times (Looking at you Sanity Docs) it scans 5-10k pages for no reason. Pages with profiles of forum members etc. I wish there was a control to limit the scan to a specific subpath or domain.
2

Thanks for the detailed feedback! Let me clear up a few things:

  1. Right now you do need to use @docs to reference documentation explicitly - this should be automatic in the next release though

  2. You actually can delete custom docs, but only if you are on the same machine as you used to add them! Head to Cursor Settings > Features > Docs and you’ll see options to manage/delete them. We know the team sharing aspect isn’t ideal right now and we’re working on improving that

  3. For the scanning issues - this usually happens with client-side rendered sites or ones with anti-bot measures. You can use the ‘prefix’ setting to limit scanning to specific domains/paths to avoid picking up irrelevant content

Check out our docs on managing custom documentation here: Cursor – @Docs

1 Like
3

Thank you for the response @danperks :slight_smile:

The issue number 2 is that even when such a doc is deleted using the method you proposed, it seems to “linger on”. If you try adding a new doc entry with the same name, for example, it will say that it already exists.

4

Hmm, thanks for the info.

I’m hoping we can get team-wide docs to be managed via the settings dashboard in the future, which should hopefully resolve these kinds of issues, but I’ll flag this to the team for now!

1 Like