Skip to content

Troubleshooting Guide

This guide provides solutions to common technical issues, error messages, and configuration problems you might encounter while using Cursor IDE, Claude Code, and MCP servers.

  1. Check system requirements

    • macOS 10.15+, Windows 10+, or Linux (64-bit)
    • At least 4GB RAM (8GB recommended)
    • 2GB free disk space
  2. Try safe mode

    Terminal window
    cursor --disable-extensions
  3. Reset user data (backup first!)

    • Windows: %APPDATA%\Cursor
    • macOS: ~/Library/Application Support/Cursor
    • Linux: ~/.config/Cursor
  4. Check for conflicting software

    • Antivirus blocking execution
    • Corporate proxy settings
    • Firewall rules

Solution: Ensure VS Code is closed during import. If that fails:

  1. Export VS Code settings manually: Code > Preferences > Profiles > Export
  2. Import in Cursor: File > Preferences > Profiles > Import

Check Plan Limits

Free tier: 2,000 completions/month Pro tier: Unlimited View usage in Settings → Subscription

Verify Indexing

Settings → Features → Codebase Indexing Should show “Indexed” status Click “Reindex” if needed

Model Status

Check status.cursor.sh Tab model might be experiencing issues Try switching to backup model

File Support

Some file types have limited support Check if your language is supported Try in a standard .js/.py file

Common causes and solutions:

  1. Wrong mode selected

    • Ensure “Agent” is selected, not “Chat”
    • Agent mode shows pencil icon
  2. File permissions

    Terminal window
    # Check file permissions
    ls -la filename
    # Fix if needed
    chmod 644 filename
  3. Git locks

    Terminal window
    # Remove git index lock
    rm .git/index.lock
  4. Read-only files

    • Check file isn’t marked read-only
    • Verify you have write access to directory
  1. Reduce @-mentioned files
  2. Use specific line ranges: @file.js:10-50
  3. Clear chat and start fresh

Your fast requests are exhausted. Options:

  1. Wait for slow requests (unlimited but delayed)
  2. Upgrade plan for more fast requests
  3. Use your API key for unlimited (pay per use)
  4. Check usage: Settings → Subscription → Usage
  1. Disable unused extensions

    • View → Extensions
    • Disable non-essential ones
  2. Reduce indexing scope

    .cursorignore
    node_modules/
    dist/
    *.log
    coverage/
  3. Clear cache

    • Cmd/Ctrl + Shift + P → “Clear Editor History”
    • Restart Cursor
  4. Check system resources

    • Close other heavy applications
    • Ensure adequate RAM available

Common with large codebases. Solutions:

  • Exclude large directories from indexing
  • Use .cursorignore aggressively
  • Consider splitting monorepo workspaces
  • Close unused editor tabs and windows
Terminal window
# Reinstall globally
npm uninstall -g @anthropic-ai/claude-code
npm install -g @anthropic-ai/claude-code
# Check installation
npm list -g @anthropic-ai/claude-code

Claude Code requires Git for Windows:

  1. Download from git-scm.com
  2. Install with “Add to PATH” option
  3. Restart terminal
  4. Verify: git --version
  1. Verify key format

    • Should start with sk-ant-
    • No extra spaces or quotes
  2. Check key permissions

    • Log into console.anthropic.com
    • Verify key is active
    • Check usage limits
  3. Set correctly

    Terminal window
    # Option 1: Environment variable
    export CLAUDE_API_KEY="sk-ant-..."
    # Option 2: During setup
    claude login
  4. Test connection

    Terminal window
    claude "hello"

For enterprise SSO:

  1. Ensure you’re on company network/VPN
  2. Check with IT for firewall rules
  3. Try: claude login --sso --verbose
  4. Use fallback API key method if needed

”Rate limit reached” after few messages

Section titled “”Rate limit reached” after few messages”

Understanding limits:

  • Pro: ~45 messages per 5-hour window
  • Max 5x: ~225 messages per 5-hour window
  • Max 20x: ~900 messages per 5-hour window

Solutions:

  1. Optimize usage

    Terminal window
    # Clear between tasks
    /clear
    # Batch related questions
    claude "1. Fix bug X 2. Add feature Y 3. Write tests"
  2. Check remaining quota

    Terminal window
    /status
  3. Use API for heavy workloads

    • Pay per token instead of message limits
    • No time-based restrictions

Configure allowed commands:

Terminal window
# Allow specific commands
claude config set allowed_commands "git,npm,ls"
# Allow file editing
claude config set auto_approve_file_edits true
  1. Check working directory

    Terminal window
    pwd # Ensure you're in right location
  2. Verify file paths

    • Claude uses paths relative to working directory
    • Check for typos in filenames
  3. Git status

    Terminal window
    git status # See what changed
    git diff # Review changes
  1. Check installation

    Terminal window
    npm list -g @modelcontextprotocol/server-name
  2. Verify configuration

    // ~/.claude/mcp.json or .mcp.json
    {
    "servers": {
    "github": {
    "command": "npx",
    "args": ["-y", "@modelcontextprotocol/github"]
    }
    }
    }
  3. Debug mode

    Terminal window
    claude --mcp-debug
  4. Check logs

    • Look for error messages in output
    • Common: missing dependencies, auth issues

GitHub MCP:

Terminal window
# Set PAT token
export GITHUB_TOKEN="ghp_..."

Database MCP:

Terminal window
# Check connection string
export DATABASE_URL="postgresql://user:pass@localhost:5432/db"
  1. Increase timeout

    {
    "servers": {
    "slow-server": {
    "command": "...",
    "timeout": 30000 // 30 seconds
    }
    }
    }
  2. Check server resources

    • Database might be overloaded
    • API rate limits
    • Network latency

Error: “Model is currently overloaded”

Section titled “Error: “Model is currently overloaded””

Meaning: The AI model servers are at capacity

Solutions:

  1. Wait a few minutes and retry
  2. Switch to a different model temporarily
  3. Use during off-peak hours
  4. Consider API usage for guaranteed availability

Check:

  1. Key starts with correct prefix
  2. No accidental spaces/characters
  3. Key hasn’t been revoked
  4. Using right key for right service

Solutions:

  1. Reduce input size
  2. Use Max mode (Cursor)
  3. Split into multiple requests
  4. Remove unnecessary context

Common causes:

  1. Wrong working directory
  2. Typo in filename
  3. File deleted/moved
  4. Case sensitivity (Linux/Mac)
  1. Export current chat (if possible)

    • Cursor: Chat menu → Export
    • Claude Code: Copy terminal output
  2. Clear problematic data

    • Cursor: Delete ~/.cursor/chats/
    • Claude Code: Start new session
  3. Restore from export

    • Paste relevant context back

Prevention:

Terminal window
# Always use git
git add -A && git commit -m "WIP: Before AI changes"

Recovery:

  1. Check editor’s local history
  2. Look for .swp or backup files
  3. Use git reflog if committed
  4. Check OS file recovery tools

Cursor:

  • Help → Toggle Developer Tools
  • Check Console for errors
  • Copy and share with support

Claude Code:

Terminal window
/doctor # Run diagnostics
/help # Show available commands
claude --version # Check version
  1. Documentation

  2. Community

  3. Official Support

    • Enterprise: Priority support
    • Pro: Email support
    • Include diagnostics output
  1. Regular updates

    Terminal window
    # Cursor: Check for updates in-app
    # Claude Code:
    npm update -g @anthropic-ai/claude-code
  2. Backup configurations

    Terminal window
    # Backup Cursor settings
    cp -r ~/.cursor ~/.cursor.backup
    # Backup Claude Code config
    cp ~/.claude.json ~/.claude.json.backup
  3. Monitor usage

    • Check quotas regularly
    • Set up usage alerts
    • Track costs for API usage
  4. Use version control

    • Commit before major AI operations
    • Use branches for experiments
    • Tag stable versions

Remember: Most issues have simple solutions. Start with the basics (restart, update, check permissions) before trying complex fixes.