windsurf-advanced-troubleshooting

# Windsurf Advanced Troubleshooting ## Overview Deep debugging techniques for Windsurf issues that resist standard troubleshooting. Covers Cascade context corruption, indexing engine problems, extension conflicts, MCP failures, and workspace configuration debugging. ## Prerequisites - Standard troubleshooting attempted (see `windsurf-common-errors`) - Terminal access - Understanding of Windsurf's architecture (VS Code base + Codeium AI layer) ## Instructions ### Step 1: Isolate Windsurf Layer vs VS Code Layer ``` Windsurf = VS Code + Codeium AI Layer If the issue is: - Editor crashes, rendering, file system → VS Code layer - AI suggestions wrong, Cascade fails, indexing stuck → Codeium layer - Extension not working → Extension compatibility layer Test VS Code layer: windsurf --disable-extensions # Run without extensions # If issue persists → VS Code layer problem Test Codeium layer: # Disable Codeium: Extensions > search "codeium" > Disable # If issue resolves → Codeium layer problem ``` ### Step 2: Debug Cascade Context Issues When Cascade consistently gives wrong or irrelevant suggestions: ```bash set -euo pipefail echo "=== Cascade Context Debug ===" # 1. Check rules file echo "--- .windsurfrules ---" if [ -f .windsurfrules ]; then CHARS=$(wc -c < .windsurfrules) echo "Size: $CHARS chars (limit: 6000)" [ "$CHARS" -gt 6000 ] && echo "WARNING: Over limit — content truncated!" else echo "MISSING — Cascade has no project context" fi # 2. Check wor...