Skip to main content 首页 创作者 jeremylongshore claude-code-plugins-plus-skills windsurf-advanced-troubleshooting
windsurf-advanced-troubleshooting Advanced Windsurf debugging for hard-to-diagnose IDE, Cascade, and indexing issues.
Use when standard troubleshooting fails, Cascade produces consistently wrong output,
or investigating deep configuration problems.
Trigger with phrases like "windsurf deep debug", "windsurf mystery error",
"windsurf impossible to fix", "cascade keeps failing", "windsurf advanced debug".
跳到安装 Skills Marketplace 发现并探索由社区构建的 Agent Skills
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill windsurf-advanced-troubleshooting命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
下载 Zip 下载中... 同仓库更多 Skills Implement user sign-up and sign-in flows with Clerk.
Use when building authentication UI, customizing sign-in experience,
or implementing OAuth social login.
Trigger with phrases like "clerk sign-in", "clerk sign-up",
"clerk login flow", "clerk OAuth", "clerk social login".
Implement session management and middleware with Clerk.
Use when managing user sessions, configuring route protection,
or implementing token refresh and custom JWT templates.
Trigger with phrases like "clerk session", "clerk middleware",
"clerk route protection", "clerk token", "clerk JWT".
Configure enterprise SSO, role-based access control, and organization management.
Use when implementing SSO integration, configuring role-based permissions,
or setting up organization-level controls.
Trigger with phrases like "clerk SSO", "clerk RBAC",
"clerk enterprise", "clerk roles", "clerk permissions", "clerk organizations".
jeremylongshore
jeremylongshore/claude-code-plugins-plus-skills
打开 GitHub 仓库 name windsurf-advanced-troubleshooting description Advanced Windsurf debugging for hard-to-diagnose IDE, Cascade, and indexing issues.
Use when standard troubleshooting fails, Cascade produces consistently wrong output,
or investigating deep configuration problems.
Trigger with phrases like "windsurf deep debug", "windsurf mystery error",
"windsurf impossible to fix", "cascade keeps failing", "windsurf advanced debug".
allowed-tools Read, Grep, Bash(ls:*), Bash(curl:*), Bash(find:*) version 1.11.0 license MIT author Jeremy Longshore <jeremy@intentsolutions.io> tags ["saas","windsurf","debugging","advanced","troubleshooting"] compatibility Designed for Claude Code, also compatible with Codex and OpenClaw
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:
set -euo pipefail
echo "=== Cascade Context Debug ==="
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
echo "--- Workspace Rules ---"
TOTAL_RULE_CHARS=0
if [ -d .windsurf/rules ]; then
for rule in .windsurf/rules/*.md; do
"$rule "
continue
wc
"$rule "
"^trigger:"
"$rule "
true
echo
" $(basename "$rule " ) : $CHARS chars, trigger: $([[ $HAS_TRIGGER -gt 0 ]] && echo 'YES' || echo 'MISSING') "
done
echo
"Total: $TOTAL_RULE_CHARS chars"
else
echo
"No .windsurf/rules/ directory"
fi
wc
echo
wc
echo
echo
"--- Total Rules Budget ---"
echo
"Project rules: $RULES_CHARS + Global rules: $GLOBAL_CHARS = $TOTAL chars (limit: 12000)"
"$TOTAL "
echo
"WARNING: Over 12000 total — rules will be truncated!"
echo
"--- Memories ---"
"$HOME /.codeium/windsurf/memories"
if
"$MEMORY_DIR "
then
"$MEMORY_DIR "
type
wc
echo
"Memory files: $MEMORY_COUNT "
"$MEMORY_COUNT "
echo
"WARNING: Many memories — may cause conflicting context"
else
echo
"No memories directory"
fi
Step 3: Debug Indexing Problems set -euo pipefail
echo "=== Indexing Debug ==="
TOTAL_FILES=$(find . -type f -not -path '*/node_modules/*' -not -path '*/.git/*' | wc -l)
echo "Total files (excluding node_modules, .git): $TOTAL_FILES "
echo "--- Large files (>1MB, not in node_modules) ---"
find . -type f -size +1M -not -path '*/node_modules/*' -not -path '*/.git/*' | head -10
if [ -f .codeiumignore ]; then
echo "--- .codeiumignore patterns ---"
wc -l < .codeiumignore
echo "patterns defined"
else
echo "WARNING: No .codeiumignore — indexing everything"
fi
if [ "$TOTAL_FILES " -gt 10000 ]; then
echo ""
echo "RECOMMENDATION: >10K files. Open a subdirectory instead of root."
echo "RECOMMENDATION: Add more patterns to .codeiumignore"
fi
Step 4: Debug Extension Conflicts set -euo pipefail
echo "=== Extension Conflict Check ==="
windsurf --list-extensions 2>/dev/null | while read ext; do
case "$ext " in
*copilot*|*tabnine*|*cody*|*intellicode*|*aws-toolkit*codewhisperer*)
echo "CONFLICT: $ext — competes with Supercomplete/Cascade"
;;
*remote*|*liveshare*|*container*)
echo "OK: $ext — compatible but may affect performance"
;;
*)
echo "OK: $ext "
;;
esac
done
echo ""
echo "Resolution: Disable conflicting extensions or run:"
echo " windsurf --disable-extensions # Test in clean mode"
Step 5: Debug MCP Server Issues set -euo pipefail
echo "=== MCP Debug ==="
MCP_CONFIG="$HOME /.codeium/windsurf/mcp_config.json"
if [ -f "$MCP_CONFIG " ]; then
echo "MCP config exists"
python3 -c "import json; json.load(open('$MCP_CONFIG '))" 2>&1 && echo "JSON: valid" || echo "JSON: INVALID"
python3 -c "
import json
config = json.load(open('$MCP_CONFIG '))
for name, server in config.get('mcpServers', {}).items():
cmd = server.get('command', 'N/A')
print(f' {name}: command={cmd}')
"
else
echo "No MCP config at $MCP_CONFIG "
fi
Step 6: Nuclear Reset Options ## Progressive Reset (least to most destructive)
1. Restart Cascade
Command Palette > "Cascade: Restart"
2. Reset Indexing
Command Palette > "Codeium: Reset Indexing"
3. Reload Window
Cmd/Ctrl+Shift+P > "Developer: Reload Window"
4. Clear Memories
Delete contents of ~/.codeium/windsurf/memories/
5. Reset All Codeium State
Close Windsurf
rm -rf ~/.codeium/windsurf/cache/
Reopen Windsurf (re-indexes, re-authenticates)
6. Clean Install
Uninstall Windsurf
rm -rf ~/.codeium/
rm -rf ~/.config/Windsurf/ # Linux
# or: rm -rf ~/Library/Application Support/Windsurf/ # macOS
Reinstall from windsurf.com/download
Error Handling Issue Cause Solution Cascade gives contradictory advice Conflicting memories Clear old memories Rules ignored Over 12K combined chars Trim rules, check total budget Wrong file suggestions Stale index Reset indexing Slow after update Extension incompatibility Test with --disable-extensions MCP tools missing Config JSON invalid Validate with python3 json parser Everything broken Corrupted state Progressive reset (Step 6)
Examples
Quick Diagnostic One-Liner echo "WS files: $(find . -not -path '*/node_modules/*' -not -path '*/.git/*' -type f | wc -l) | Rules: $(wc -c < .windsurfrules 2>/dev/null || echo 0) c | Ignore: $(wc -l < .codeiumignore 2>/dev/null || echo 0) patterns | Exts: $(windsurf --list-extensions 2>/dev/null | wc -l) "
Submit Support Ticket Attach:
1. Output from all diagnostic scripts above
2. Debug bundle from windsurf-debug-bundle
3. Exact prompts that produce wrong results
4. Expected vs actual Cascade behavior
Resources
Next Steps For load and scale patterns, see windsurf-load-scale.
