I have added a few online doc indexes and I would like my agents to search in particular pages where I know the documentation for a specific problem.
I have had some problems with agents unable to find the correct documentation for a specific class or using the wrong doc page.
So I would like to be able to restrain their search to a specific page or group of page whithout having to create a new documentation index for that specific page.
Could be as the form of a @ mention with / or other separator for focus the search on a specific page.
Thank you for the feature request. I think thats a great idea as developers often have good knowledge of docu that is required, so I upvoted it as well.
Cursor Team reviews and considers feature requests regularly.
You could create a rule that they are to maintain and and here to a serch_restraints.md (although it wouldbe good to put your restraint policies in a sqlite .db - and have that be a part of your prompt /rules "Always check the search_restraints before executing. Think explain your search_restraints, keep a development_diary.md - and update the search success in the .db upon completion - you will ask me your performance number 1-5 for the task and you will update the db for that prompt. Understand?
So I do really strict and verbose project scaffolding:
I do a TON of preflight scoffolding on the project before dev - and I have these strict rules of engagement for keeping agentic context over long periogd…
