Cursor search feature not scanning one script
Environment
- Cursor Version: 0.44.11
- VS Code Version: 1.93.1
- Not a git repository
Issue Description
Our codebase contains about twenty Python files and log files, but Cursor’s search functionality in the chat tab appears to be artificially limited in its scope, preventing it from finding the most relevant file for the query. When asked to identify a script that extracts CSV data, Cursor only searches through 5 files, all with similar confidence scores around 0.50-0.54, while completely missing the relevant extract.py
file that exists in the same directory.
What I’m Seeing
- In my directory, I have multiple Python files including a specifically named
extract.py
that handles CSV data extraction - When asking Cursor to identify which script handles data extraction, it returns only:
- main.py (0.54)
- app-20-12-24.log (0.52)
- app.log (0.52)
- main_final2.py (0.50)
- main_final.py (0.50)
- The search appears to be truncated at 5 files, missing many other files in the codebase
- The confidence scores are all clustered around 0.50, suggesting limited analysis of file content relevance!
Steps to Reproduce
- Open a Python codebase without git initialized containing multiple files including a dedicated script that does one thing (ie. extract data from a CSV file)
- Use Cursor’s chat feature (model: gpt-4o, or claude 3.5) to ask “which script of our codebase was only designed to extract CSV data”
- Observe the search results
Attempted Solutions
- Resynced the index
- Added explicit comments in the scripts to better describe their functionality
- Verified file existence and visibility in the directory
Expected Behavior
- Cursor should scan all files in the codebase
extract.py
should be identified with high confidence as it directly matches the search criteria- Search results should show varying confidence scores based on actual relevance
Actual Behavior
- Only 5 files are scanned
- Relevant
extract.py
file is completely missed - All confidence scores are similarly low (~0.50)
- Search appears to be arbitrarily limited rather than comprehensive
Would appreciate any insights into whether this is a known bug with a a fix or a bad usage.
Thank you