windsurf-common-errors
Quickly identify and fix common Windsurf and Cascade IDE errors including connectivity and indexing issues.
Install
mkdir -p .claude/skills/windsurf-common-errors && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/6908" && unzip -o skill.zip -d .claude/skills/windsurf-common-errors && rm skill.zipInstalls to .claude/skills/windsurf-common-errors
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.
Diagnose and fix common Windsurf IDE and Cascade errors.Key capabilities
- →Diagnose Cascade not responding issues
- →Troubleshoot Supercomplete not showing suggestions
- →Resolve indexing stuck or slow problems
- →Identify and fix extension conflicts
- →Address Cascade writing to wrong files
How it works
The skill provides a quick reference guide for common Windsurf IDE errors by listing symptoms and offering specific solutions, such as checking internet connection, restarting components, or modifying configuration files.
Inputs & outputs
When to use windsurf-common-errors
- →Fixing Cascade unresponsiveness
- →Resolving Supercomplete suggestion failures
- →Troubleshooting Windsurf slow performance
- →Handling extension conflicts in Windsurf
About this skill
Windsurf Common Errors
Overview
Quick reference for the most common Windsurf IDE errors and their solutions. Covers Cascade failures, Supercomplete issues, indexing problems, and extension conflicts.
Prerequisites
- Windsurf installed and previously working
- Access to Windsurf settings and logs
Instructions
Error 1: Cascade Not Responding
Symptoms: Cascade panel shows spinner indefinitely, no response to prompts.
Solutions:
- Check internet connection -- Cascade requires cloud access
- Check Windsurf status: https://status.windsurf.com
- Check credit balance: Windsurf widget (status bar) > Account
- Restart Cascade: Command Palette > "Cascade: Restart"
- Restart Windsurf: Cmd/Ctrl+Shift+P > "Reload Window"
Error 2: Supercomplete Not Showing Suggestions
Symptoms: No ghost text appears while typing.
Solutions:
- Check if disabled: Click Windsurf widget (status bar) > verify autocomplete is ON
- Check file type: Supercomplete may be disabled for certain languages
- Check
.codeiumignore: Current file might be excluded from indexing - Ensure not conflicting: Disable GitHub Copilot or TabNine if installed
// Verify in settings.json
{
"editor.inlineSuggest.enabled": true,
"codeium.autocomplete.enable": true
}
Error 3: Indexing Stuck or Slow
Symptoms: Status bar shows "Indexing..." for extended periods, Cascade lacks context.
Solutions:
- Check workspace size: Windsurf struggles with 100K+ files without ignore rules
- Create or update
.codeiumignore:
node_modules/
.git/
dist/
build/
.next/
coverage/
vendor/
__pycache__/
*.min.js
*.bundle.js
*.map
- Open a subdirectory instead of monorepo root
- Command Palette > "Codeium: Reset Indexing"
Error 4: Extension Conflicts
Symptoms: Duplicate suggestions, slow editor, features not working.
Known conflicts:
GitHub Copilot — conflicts with Supercomplete (disable one)
TabNine — conflicts with Supercomplete
Cody (Sourcegraph) — conflicts with Cascade
IntelliCode — may interfere with completions
Fix: Disable conflicting extensions:
Extensions sidebar > Search "copilot" > Disable
Error 5: Cascade Writes to Wrong Files
Symptoms: Cascade modifies files you didn't intend.
Solutions:
- Be specific in prompts: name exact file paths
- Add constraints: "Don't modify any files except src/services/auth.ts"
- Use
.windsurfignoreto protect sensitive directories - Review diffs before accepting -- use the Revert button per step
- Always commit before Cascade sessions for safe rollback
Error 6: "Model not available" or Credit Exhausted
Symptoms: "You've used all your credits" or specific model unavailable.
Solutions:
- Free plan: 25 credits/month. Switch to SWE-1 Lite (unlimited)
- Pro plan: 500 credits/month. Buy additional credits at windsurf.com/account
- Switch model: Use the model dropdown in Cascade to select a different model
- Check credit usage: Windsurf widget > Account > Usage
Error 7: MCP Server Not Connecting
Symptoms: MCP tools not appearing in Cascade, "server disconnected" errors.
Solutions:
- Verify MCP is enabled: Settings > Cascade > MCP > Enable
- Check config file:
~/.codeium/windsurf/mcp_config.json - Verify command exists: Run the MCP command manually in terminal
- Check environment variables: MCP config supports
${VAR}interpolation - Restart: Command Palette > "Cascade: Restart MCP Servers"
Error 8: Cascade Loses Context Mid-Conversation
Symptoms: Cascade forgets what it was doing, makes contradictory changes.
Solutions:
- Keep conversations focused: one task per Cascade session
- Start a new conversation for new tasks (Cmd/Ctrl+L, then + icon)
- Use @ mentions to re-inject context:
@src/services/auth.ts - Convert key decisions to Memories: "Remember that we're using JWT, not sessions"
- For long tasks, use Workflows instead of multi-turn conversations
Error Handling
| Issue | Quick Fix | Root Cause |
|---|---|---|
| No AI features | Check auth in status bar | Token expired, re-sign-in |
| Cascade slow | Add .codeiumignore | Indexing too many files |
| Wrong suggestions | Update .windsurfrules | Missing project context |
| Preview broken | Close and re-open Preview | Dev server disconnected |
| Terminal errors | Cmd/Ctrl+Shift+. | Auto-debug via Cascade |
Examples
Quick Health Check
# Check if Windsurf is installed
windsurf --version
# Check Codeium auth state
ls ~/.codeium/
Reset Everything
Command Palette (Cmd/Ctrl+Shift+P):
1. "Codeium: Reset Indexing"
2. "Cascade: Restart"
3. "Developer: Reload Window"
Resources
Next Steps
For comprehensive debugging, see windsurf-debug-bundle.
When not to use it
- →When the issue is not related to Windsurf IDE or Cascade
- →When the problem is outside the scope of common errors
- →When the user lacks access to Windsurf settings or logs
Prerequisites
Limitations
- →Windsurf struggles with 100K+ files without ignore rules
- →Supercomplete may be disabled for certain languages
- →Known conflicts exist with GitHub Copilot, TabNine, Cody, and IntelliCode
How it compares
This skill offers targeted solutions for specific Windsurf IDE errors, unlike general debugging approaches.
Compared to similar skills
windsurf-common-errors side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| windsurf-common-errors (this skill) | 1 | 27d | Review | Beginner |
| godot | 1,044 | 5mo | Review | Intermediate |
| python-testing-patterns | 77 | 2mo | Review | Intermediate |
| error-handling-patterns | 35 | 2mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
godot
bfollington
This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.
python-testing-patterns
wshobson
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
error-handling-patterns
wshobson
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
chrome-devtools
mrgoonie
Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automation, and JavaScript debugging.
unreal-engine-cpp-pro
sickn33
Expert guide for Unreal Engine 5.x C++ development, covering UObject hygiene, performance patterns, and best practices.
python-performance-optimization
wshobson
Profile and optimize Python code using cProfile, memory profilers, and performance best practices. Use when debugging slow Python code, optimizing bottlenecks, or improving application performance.