Windsurf Cascade stuck, looping or freezing?
A spinner alone cannot distinguish planning, an active command, workspace scanning, or a stalled interface. Observe process and file activity before testing a narrower workspace.
What the failure looks like.
The plan remains on screen, the spinner continues, and CPU or memory climbs while the repository produces no clear next action.
Why it happens.
A spinner does not identify the cause. Official documentation describes indexing overhead and ignored paths; investigate those only when process activity and a controlled scope comparison support the hypothesis.
Fix it without losing the task.
What the next AI should receive.
Windsurf version, workspace and ignored-path scope, visible plan progress, CPU/disk or terminal activity, changed files, one indexing/scope comparison, and its result.
Check before restarting
Check whether the plan is still changing, a command is running, or the UI is only showing a spinner. Preserve the working tree before narrowing workspace scope or restarting.
Boundary of the evidence
Repository size and indexing are possible factors, not a confirmed cause from the spinner alone. A narrower workspace test can provide evidence but is not a guaranteed fix.
Diagnostic checkpoint
A narrower workspace test is useful only when its scope and observed progress are recorded for comparison.
Workspace scope evidence.
Official indexing and ignore-file guidance, checked September 27, 2026, explains excluded paths and legacy ignore filenames. Current vendor documentation uses Devin Desktop naming. This supports a reversible scope test, not a diagnosis that indexing caused your spinner.
FAQ.
Does a Cascade spinner mean indexing is the cause?
Not by itself. Check visible progress, process activity, active terminal work, and logs. Treat repository indexing as a hypothesis until a controlled scope comparison supports it.
Should I add every large folder to .codeiumignore?
No. Exclude only paths that are generated, vendor, or irrelevant to the task, and check the current Windsurf guidance. Preserve the original ignore rules so the change can be reversed.
Scope note: Evidence boundary: use this as a diagnostic workflow, not a verified Windsurf-specific root-cause report. Change one workspace or indexing variable at a time and keep the result.
Cascade repeats edits that do not converge.
A repeated edit and a frozen IDE are different symptoms. This section addresses visible changes that fail to converge; issue #284 describes a different freeze symptom and is not evidence for an edit-loop defect.
- Identify the exact file and acceptance condition that is not converging. Keep one before/after diff for each repeated edit.
- Stop the request if it is writing the same change again. Confirm whether a terminal command or tool call is still active before retrying.
- Restart with one small, measurable change and state the check that will decide whether it succeeded. Do not use a full IDE restart as the first diagnostic step.
- If it repeats, preserve the prompt, diff, Windsurf version, and tool output for a reproducible report. Treat the underlying cause as unknown until evidence supports it.
Windsurf issue #284 describes an IDE freeze after a Cascade response, not a repeated-edit loop. It is not evidence for the loop described by this page.
Windsurf freezes after a Cascade response.
Clicks, scrolling, and keyboard input stop working after a Cascade response. Some reports describe a freeze lasting several minutes.
- Wait briefly if the IDE process is alive and responsive elsewhere. Record which surface is frozen and whether a terminal command continues.
- Save any open editor buffers if possible. Capture the completed Cascade response and the time of the freeze before restarting.
- After restart, inspect the current diff, changed files, and process output. Do not replay the full task until you know what the completed response already changed.
- If reporting the issue, include version, OS, reproduction steps, and logs with secrets removed; distinguish observed traces from root-cause conclusions.
Issue #284 is one Linux x64 report for Windsurf 1.9544.35 (1.106.0); its renderer and gRPC traces are user-collected, not a vendor-confirmed cause or fix.
Additional symptom sources.
How ShardStitch helps.
ShardStitch can preserve the current task boundary and local diff while you distinguish a running command, workspace scan, and stalled interface. It cannot inspect Windsurf indexing internals or stop a remote/model request.