WI

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.zip

Installs 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.
56 charsno explicit “when” trigger
Beginner

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

You give it
Windsurf IDE symptoms or error messages
You get back
Solutions to common Windsurf IDE and Cascade errors

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:

  1. Check internet connection -- Cascade requires cloud access
  2. Check Windsurf status: https://status.windsurf.com
  3. Check credit balance: Windsurf widget (status bar) > Account
  4. Restart Cascade: Command Palette > "Cascade: Restart"
  5. Restart Windsurf: Cmd/Ctrl+Shift+P > "Reload Window"

Error 2: Supercomplete Not Showing Suggestions

Symptoms: No ghost text appears while typing.

Solutions:

  1. Check if disabled: Click Windsurf widget (status bar) > verify autocomplete is ON
  2. Check file type: Supercomplete may be disabled for certain languages
  3. Check .codeiumignore: Current file might be excluded from indexing
  4. 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:

  1. Check workspace size: Windsurf struggles with 100K+ files without ignore rules
  2. Create or update .codeiumignore:
node_modules/
.git/
dist/
build/
.next/
coverage/
vendor/
__pycache__/
*.min.js
*.bundle.js
*.map
  1. Open a subdirectory instead of monorepo root
  2. 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:

  1. Be specific in prompts: name exact file paths
  2. Add constraints: "Don't modify any files except src/services/auth.ts"
  3. Use .windsurfignore to protect sensitive directories
  4. Review diffs before accepting -- use the Revert button per step
  5. 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:

  1. Verify MCP is enabled: Settings > Cascade > MCP > Enable
  2. Check config file: ~/.codeium/windsurf/mcp_config.json
  3. Verify command exists: Run the MCP command manually in terminal
  4. Check environment variables: MCP config supports ${VAR} interpolation
  5. 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:

  1. Keep conversations focused: one task per Cascade session
  2. Start a new conversation for new tasks (Cmd/Ctrl+L, then + icon)
  3. Use @ mentions to re-inject context: @src/services/auth.ts
  4. Convert key decisions to Memories: "Remember that we're using JWT, not sessions"
  5. For long tasks, use Workflows instead of multi-turn conversations

Error Handling

IssueQuick FixRoot Cause
No AI featuresCheck auth in status barToken expired, re-sign-in
Cascade slowAdd .codeiumignoreIndexing too many files
Wrong suggestionsUpdate .windsurfrulesMissing project context
Preview brokenClose and re-open PreviewDev server disconnected
Terminal errorsCmd/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

Windsurf installed and previously workingAccess to Windsurf settings and logs

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.

SkillInstallsUpdatedSafetyDifficulty
windsurf-common-errors (this skill)127dReviewBeginner
godot1,0445moReviewIntermediate
python-testing-patterns772moReviewIntermediate
error-handling-patterns352moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

More by jeremylongshore

View all by jeremylongshore

analyzing-logs

jeremylongshore

Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.

14123

ollama-setup

jeremylongshore

Configure auto-configure Ollama when user needs local LLM deployment, free AI alternatives, or wants to eliminate hosted API costs. Trigger phrases: "install ollama", "local AI", "free LLM", "self-hosted AI", "replace OpenAI", "no API costs". Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

1167

backtesting-trading-strategies

jeremylongshore

Backtest crypto and traditional trading strategies against historical data. Calculates performance metrics (Sharpe, Sortino, max drawdown), generates equity curves, and optimizes strategy parameters. Use when user wants to test a trading strategy, validate signals, or compare approaches. Trigger with phrases like "backtest strategy", "test trading strategy", "historical performance", "simulate trades", "optimize parameters", or "validate signals".

1071

generating-database-seed-data

jeremylongshore

Process this skill enables AI assistant to generate realistic test data and database seed scripts for development and testing environments. it uses faker libraries to create realistic data, maintains relational integrity, and allows configurable data volumes. u... Use when working with databases or data models. Trigger with phrases like 'database', 'query', or 'schema'.

1033

cursor-codebase-indexing

jeremylongshore

Execute set up and optimize Cursor codebase indexing. Triggers on "cursor index setup", "codebase indexing", "index codebase", "cursor semantic search". Use when working with cursor codebase indexing functionality. Trigger with phrases like "cursor codebase indexing", "cursor indexing", "cursor".

885

testing-mobile-apps

jeremylongshore

Execute mobile app testing on iOS and Android devices/simulators. Use when performing specialized testing. Trigger with phrases like "test mobile app", "run iOS tests", or "validate Android functionality".

810

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.

1,0441,947

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.

77204

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.

35170

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.

41157

unreal-engine-cpp-pro

sickn33

Expert guide for Unreal Engine 5.x C++ development, covering UObject hygiene, performance patterns, and best practices.

43117

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.

27131

Search skills

Search the agent skills registry