Troubleshoot Cursor codebase indexing: stuck indexing, empty search, @codebase failures, and performance issues. Triggers on "cursor indexing", "cursor index", "@codebase not working", "cursor search broken", "indexing stuck".
89
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Diagnose and fix codebase indexing problems. Covers stuck indexing, empty search results, stale results, and performance optimization for large codebases.
| Symptom | Likely Cause | Quick Fix |
|---|---|---|
| Status bar stuck on "Indexing..." | Large codebase or network issue | Add .cursorignore, resync |
| @Codebase returns nothing | Index not built or file excluded | Wait for index, check ignore files |
| @Codebase finds wrong code | Stale index | Resync index |
| Indexing crashes / restarts | Memory or file watcher limits | Increase limits, reduce scope |
| "Unable to index" error | Network blocked or auth expired | Check proxy/firewall, re-auth |
Create or update .cursorignore in project root:
# .cursorignore -- exclude non-essential directories
# Build output
dist/
build/
.next/
out/
target/
# Dependencies (always exclude)
node_modules/
vendor/
.venv/
venv/
# Generated / large files
*.min.js
*.min.css
*.bundle.js
*.map
*.lock
package-lock.json
yarn.lock
pnpm-lock.yaml
# Data files
*.csv
*.sql
*.sqlite
*.parquet
*.json.gz
fixtures/
# Media
*.png
*.jpg
*.gif
*.svg
*.mp4
*.woff2Cmd+Shift+P > Cursor: Resync Index
# macOS
rm -rf ~/Library/Application\ Support/Cursor/Cache/
rm -rf ~/Library/Application\ Support/Cursor/CachedData/
# Linux
rm -rf ~/.config/Cursor/Cache/
rm -rf ~/.config/Cursor/CachedData/
# Windows (PowerShell)
Remove-Item -Recurse "$env:APPDATA\Cursor\Cache"
Remove-Item -Recurse "$env:APPDATA\Cursor\CachedData"Restart Cursor after clearing cache. Full re-index begins automatically.
Look at the bottom status bar. If it says "Indexing...", wait for it to finish. For projects with 10K+ files, initial indexing can take 10-30 minutes.
A file might be excluded by:
.gitignore (Cursor respects this by default).cursorignore (explicit exclusion).cursorindexingignore (excluded from index but not from AI features)Verify: Cursor Settings > Features > Codebase Indexing > View included files
This opens a text file listing all indexed paths. Search for the file you expect to find.
Indexing requires network access to Cursor's embedding API. Test:
api.cursor.com?@Codebase uses semantic search (embeddings), not keyword matching. The query "authentication middleware" will find files about auth even if they never use the word "middleware." But it may miss files if the semantic meaning is very different from the query.
For exact keyword matching, use Cmd+Shift+F (workspace search) instead.
Cursor re-checks for file changes every 10 minutes using a Merkle tree. If you need fresher results:
Cmd+Shift+P > Cursor: Resync Index@Codebase query| Project Size | Files Indexed | Initial Index Time |
|---|---|---|
| Small (< 1K files) | ~500 | < 30 seconds |
| Medium (1K-10K files) | ~5,000 | 1-5 minutes |
| Large (10K-50K files) | ~20,000 | 5-30 minutes |
| Very large (50K+) | ~50,000+ | 30 min - 2 hours |
Do not open the entire monorepo root. Instead:
# Open just the package you're working on:
cursor packages/api/
# Or use .cursorignore to exclude other packages:
# .cursorignore
packages/web/
packages/mobile/
packages/admin/
packages/deprecated-*If indexing crashes on Linux with large projects:
# Check current limit
cat /proc/sys/fs/inotify/max_user_watches
# Increase to 524288 (persists across reboots)
echo "fs.inotify.max_user_watches=524288" | sudo tee -a /etc/sysctl.conf
sudo sysctl -pIf Cursor runs out of memory during indexing:
// settings.json
{
"files.maxMemoryForLargeFilesMB": 4096,
"files.watcherExclude": {
"**/node_modules/**": true,
"**/.git/**": true,
"**/dist/**": true,
"**/build/**": true
}
}| File | Indexed? | Available to AI? | Use Case |
|---|---|---|---|
Listed in .cursorignore | No | No (best effort) | Secrets, large binaries, build output |
Listed in .cursorindexingignore | No | Yes (via @Files) | Test fixtures, docs, large but useful files |
| Not in any ignore file | Yes | Yes | Your source code |
Use .cursorindexingignore for files you want to reference explicitly but not have polluting search results:
# .cursorindexingignore
tests/fixtures/large-sample.json
docs/api-spec.yaml
e2e/recordings/.cursorignore proactively for regulated data3a2d27d
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.