CU

cursor-indexing-issues

Diagnostic guide to fix stuck indexing, broken codebase search, and @codebase failures in Cursor.

Install

mkdir -p .claude/skills/cursor-indexing-issues && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/1702" && unzip -o skill.zip -d .claude/skills/cursor-indexing-issues && rm skill.zip

Installs to .claude/skills/cursor-indexing-issues

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Troubleshoot Cursor codebase indexing: stuck indexing, empty search,
68 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Reduce indexing scope with .cursorignore files
  • Resync the Cursor index manually
  • Clear Cursor cache directories
  • Verify if a file is excluded from indexing
  • Check network connectivity for embedding API access
  • Optimize performance for large projects

How it works

The skill diagnoses indexing problems by checking symptoms like stuck indexing or empty search results. It provides steps to modify ignore files, resync the index, clear caches, and adjust system limits.

Inputs & outputs

You give it
Cursor project codebase and configuration files like .cursorignore
You get back
Resolved Cursor indexing issues, optimized indexing performance, or diagnostic information

When to use cursor-indexing-issues

  • Fixing stuck 'Indexing...' status bar
  • Resolving empty @codebase search results
  • Managing memory limits during indexing
  • Configuring .cursorignore files

About this skill

Cursor Indexing Issues

Diagnose and fix codebase indexing problems. Covers stuck indexing, empty search results, stale results, and performance optimization for large codebases.

Quick Diagnosis

SymptomLikely CauseQuick Fix
Status bar stuck on "Indexing..."Large codebase or network issueAdd .cursorignore, resync
@Codebase returns nothingIndex not built or file excludedWait for index, check ignore files
@Codebase finds wrong codeStale indexResync index
Indexing crashes / restartsMemory or file watcher limitsIncrease limits, reduce scope
"Unable to index" errorNetwork blocked or auth expiredCheck proxy/firewall, re-auth

Fix: Stuck Indexing

Step 1: Reduce Scope

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
*.woff2

Step 2: Resync Index

Cmd+Shift+P > Cursor: Resync Index

Step 3: Clear Cache (if resync fails)

# 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.

Fix: @Codebase Returns No Results

Check 1: Is Indexing Complete?

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.

Check 2: Is the File Excluded?

A file might be excluded by:

  1. .gitignore (Cursor respects this by default)
  2. .cursorignore (explicit exclusion)
  3. .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.

Check 3: Network Connectivity

Indexing requires network access to Cursor's embedding API. Test:

  • Can you access api.cursor.com?
  • Is a corporate proxy blocking outbound HTTPS?
  • Is a VPN interfering?

Check 4: Semantic vs Keyword Search

@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.

Fix: Stale / Outdated Results

Cursor re-checks for file changes every 10 minutes using a Merkle tree. If you need fresher results:

  1. Save all open files
  2. Cmd+Shift+P > Cursor: Resync Index
  3. Wait for "Indexed" status to reappear
  4. Retry your @Codebase query

Performance Optimization for Large Projects

Indexing Time Benchmarks

Project SizeFiles IndexedInitial Index Time
Small (< 1K files)~500< 30 seconds
Medium (1K-10K files)~5,0001-5 minutes
Large (10K-50K files)~20,0005-30 minutes
Very large (50K+)~50,000+30 min - 2 hours

Monorepo Strategy

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-*

Linux File Watcher Limits

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 -p

Memory Pressure

If Cursor runs out of memory during indexing:

// settings.json
{
  "files.maxMemoryForLargeFilesMB": 4096,
  "files.watcherExclude": {
    "**/node_modules/**": true,
    "**/.git/**": true,
    "**/dist/**": true,
    "**/build/**": true
  }
}

.cursorignore vs .cursorindexingignore

FileIndexed?Available to AI?Use Case
Listed in .cursorignoreNoNo (best effort)Secrets, large binaries, build output
Listed in .cursorindexingignoreNoYes (via @Files)Test fixtures, docs, large but useful files
Not in any ignore fileYesYesYour 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/

Enterprise Considerations

  • Data residency: Embeddings stored in Turbopuffer cloud. No plaintext code stored, but metadata (obfuscated filenames) exists server-side
  • Air-gapped environments: Indexing requires outbound HTTPS. Not available in fully air-gapped setups
  • Index freshness SLA: 10-minute polling interval is not configurable. Manual resync is the only way to force immediate re-index
  • Audit: No logging of which files are indexed. Use .cursorignore proactively for regulated data

Resources

When not to use it

  • When performing exact keyword matching searches
  • When network access to api.cursor.com is blocked

Limitations

  • Initial indexing for projects with 10K+ files can take 10-30 minutes
  • Cursor re-checks for file changes every 10 minutes
  • Indexing requires network access to Cursor's embedding API

How it compares

This skill provides specific commands and configuration adjustments for Cursor's indexing system, unlike manually troubleshooting general application performance issues.

Compared to similar skills

cursor-indexing-issues side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
cursor-indexing-issues (this skill)327dReviewIntermediate
python-testing-patterns772moReviewIntermediate
error-handling-patterns352moNo flagsIntermediate
codex-claude-loop139moReviewAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

More by jeremylongshore

View all by jeremylongshore

analyzing-logs

jeremylongshore

Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.

14123

ollama-setup

jeremylongshore

Configure auto-configure Ollama when user needs local LLM deployment, free AI alternatives, or wants to eliminate hosted API costs. Trigger phrases: "install ollama", "local AI", "free LLM", "self-hosted AI", "replace OpenAI", "no API costs". Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

1167

backtesting-trading-strategies

jeremylongshore

Backtest crypto and traditional trading strategies against historical data. Calculates performance metrics (Sharpe, Sortino, max drawdown), generates equity curves, and optimizes strategy parameters. Use when user wants to test a trading strategy, validate signals, or compare approaches. Trigger with phrases like "backtest strategy", "test trading strategy", "historical performance", "simulate trades", "optimize parameters", or "validate signals".

1071

generating-database-seed-data

jeremylongshore

Process this skill enables AI assistant to generate realistic test data and database seed scripts for development and testing environments. it uses faker libraries to create realistic data, maintains relational integrity, and allows configurable data volumes. u... Use when working with databases or data models. Trigger with phrases like 'database', 'query', or 'schema'.

1033

cursor-codebase-indexing

jeremylongshore

Execute set up and optimize Cursor codebase indexing. Triggers on "cursor index setup", "codebase indexing", "index codebase", "cursor semantic search". Use when working with cursor codebase indexing functionality. Trigger with phrases like "cursor codebase indexing", "cursor indexing", "cursor".

885

testing-mobile-apps

jeremylongshore

Execute mobile app testing on iOS and Android devices/simulators. Use when performing specialized testing. Trigger with phrases like "test mobile app", "run iOS tests", or "validate Android functionality".

810

You might also like

Search skills

Search the agent skills registry