Skip to main content

Troubleshooting Codebase Reading Issues

info

If Cursor is having trouble reading your codebase or files, follow this guide to resolve common issues.

Common Symptoms​

  1. Cursor can't see project files
  2. AI features not working with codebase
  3. File tree not updating
  4. Search functionality not working

Quick Fixes​

1. Refresh the File Tree​

The fastest solution is often to refresh your file tree:

  1. Right-click on the file explorer
  2. Select "Refresh"
  3. Wait for the file tree to update

2. Check File Permissions​

  1. Right-click on your project folder
  2. Select "Properties"
  3. Go to "Security" tab
  4. Ensure your user has "Read" and "Write" permissions

3. Verify .gitignore and .cursorignore​

Sometimes files are intentionally ignored. Check:

  1. .gitignore file contents
  2. .cursorignore file contents
  3. Remove any patterns that shouldn't be ignored

Deep Dive Solutions​

File System Watcher Issues​

If Cursor isn't detecting file changes:

.vscode/settings.json
{
  "files.watcherExclude": {
    "**/node_modules/**": true,
    "**/dist/**": true,
    // Add other directories you want to exclude
  }
}

Large Codebase Handling​

For large codebases:

  1. Increase Memory Limit

    .cursor/settings.json
    {
      "files.maxMemoryForLargeFilesMB": 4096
    }

  2. Optimize File Watching

    • Exclude unnecessary directories
    • Use workspace trust features
    • Consider using workspace storage

Git Integration Issues​

If Git-related features aren't working:

  1. Check Git installation:

    git --version

  2. Verify Git configuration:

    git config --list

  3. Reset Git cache:

    git rm -r --cached .
    git add .

Prevention Tips​

  1. Clean Project Structure

    • Organize files logically
    • Use appropriate .gitignore
    • Keep root directory clean

  2. Regular Maintenance

    • Clear editor cache regularly
    • Update Cursor frequently
    • Monitor system resources

  3. Performance Optimization

    • Exclude large binary files
    • Use workspace storage
    • Implement proper ignore patterns

Advanced Troubleshooting​

Logging and Diagnostics​

Enable detailed logging:

  1. Open Command Palette (Ctrl/Cmd + Shift + P)
  2. Type "Developer: Set Log Level"
  3. Select "Trace"

Cache Reset​

If problems persist:

  1. Close Cursor
  2. Delete cache directories:
    • Windows: %APPDATA%\Cursor\Cache
    • macOS: ~/Library/Application Support/Cursor/Cache
    • Linux: ~/.config/Cursor/Cache
  3. Restart Cursor

Workspace Trust​

Configure workspace trust:

  1. Open Command Palette
  2. Search for "Workspace Trust"
  3. Configure trust settings for your project

When to Contact Support​

Contact Cursor support if:

  1. Issues persist after trying all solutions
  2. You encounter data loss
  3. Performance degrades significantly
  4. You find security concerns
tip

Keep your error logs and system information ready when contacting support