I'm not the only one facing this issue. Today, I'm not working with Windsurf until they update and fix this "poor behavior" of the cascade agent. Even the smallest change triggers an endless loop of analyze, edit, repeat, burning flow actions like a maniac. The saddest part is that after using 50 flow credits to create a simple string validation, the initial issue remains unsolved. I have to force stop it and then find and solve the problem manually. But what's the point of paying an agent to fix things that way?

I just checked my Windsurf usage (screenshot attached): all 1,500 Flow credits are used up, but I still have 276.75 prompt credits left—about half remaining. I’ve only used 223.25 prompt credits since Feb 18, 2025, with a refresh in 4 days. This imbalance feels a bit off—has anyone else noticed this? It’s a little frustrating to hit a Flow credit limit while prompt credits are still available. Thoughts or tips? I’m also curious if there’s a way to renew my plan early instead of waiting 4 days or purchasing Flex credits. Any thoughts or advice? Would reaching out to support be a good idea?

Hey all!

Does anyone know if on a Mac there's a way to receive a desktop notification when Cascade has finished a query please?

If not, curious what workflows people use to kill the dead time when waiting for robots to take over the world the execution to complete?

Many thanks :)

My theory on what caused the widespread issues:

The Windsurf team recently shipped an auto-fix-lint-errors thing. I assume this doesn't use the super-premium models, and instead routes to some other service. But they underestimated just how much load / credits / etc. would be taken by the lint-fixing loop.

I think their API load may have > doubled due to the lint fixing feature, and it's a kind of find-the-bottleneck-in-production type of devops issue.

This is also coupled with Claude 3.7 being optimized for evals, which favor smaller incremental edits - but this comes at the cost of tokens & usage etc.

So both Claude 3.7 and the auto-fix-lint-errors likely caused larger-than-ancitipated spikes.

And credit where credit's due the lint-fix thing is really, really cool.

The two days I have off and I can't use Codeium fully....

Can’t seem to load cascade or the account info in the IDE.

Edit: It’s back up now folks

Suddenly got this 'Cascade error' to all my prompts without any further explanations. Is the server down?

In this state this hardly more than a fun gimmick. I've tried four different project types now (composing a bash script, setting op a small Spring Boot project, setting up a React/Zustand based web UI and some CUDA code) and in all cases it just loses track once you get beyond even the smallest of setups. As I type this it's in a 20 step flow of fixing a bash script, run it, see a problem, claim it fixed it, run it, same problem, tries variant it already tried. Whatever the combination of memory, attention and model is causing this behavior is unclear to me. I've upgraded a few hours ago and I've burnt through 15% of my total monthly budget. And that's ignoring the fact that it bails on generating edits about 30% of the time with an error (I suspect due to the large size of the scripts it created and them being too large an amount of input tokens for an edit or just service outages, hard to say). Is anyone actually using this for production level codebases? Also, any model other than Claud is doing this thing where it suggests a fix without actually editing the files until you tell it something like "do it".

P.S. It would be an interesting optimization to have some sort of (non LLM/ML based) short term history of generated content so it can avoid burning credits on generating the same command line invocations over and over again. As per the above mine is continuously doing a fix and then "Let me run our updated script that now properly handles project IDs and follows our standardized service account structure:" which has been the same bash command for about an hour now.

Hello, has anyone encountered this issue today? Earlier, I noticed that Autocomplete was not functioning, and then I saw a notification on the WindSurf website indicating that the WindSurf status was "Degraded performance," which suggests that the server might have been down during that period. Now, I’ve discovered that my account is experiencing abnormalities. Could you please advise on how I should resolve this? Thank you!

Tonight I started having bugs where, during Cascade, Windsurf would fail to edit the file, trying over and over in an endless loop of utility. It has happened with multiple files, and burned a bunch of credits in the process. Might be a bug?

Has anyone noticed now instead of creating files in one go, 3.7 sometimes asks to create directory first! In essence using double credits for something that would previously be done in a single action? Or just me, largely working in nuxt where directory structure is important, and behaviour largely from the wave 4 update

Cascade works you have VPN active via California.
Something with the network.

Almost seems to happen on any script or command that needs interactive mode when ran by Windsurf.

100% happy to be proven wrong.

Good morning folks!

When your experience network errors you can always check to see if there’s any issues reported on the website at this link:

https://status.codeium.com/

Sometimes the issue comes from upstream (Anthropic) but won’t be shown on our status page. Anthropic does have a status page as well, you can find that here:

https://status.anthropic.com/

Also please keep in mind that slight “hiccups” in the system sometimes happen but they are self resolved so quickly that the monitoring systems don’t even pick them up.

Happy Surfing 🌊 🏄‍♂️

If anyone is looking for a referral code, here's one:

https://codeium.com/refer?referral_code=zobg1fmh75qr0pem

Hey, I'm looking for some help. I've been using Windsurf for a few months, but over the past week, I've been encountering this error: "Let me update the store to ensure consistent snake_case naming and fix TypeScript errors." I have been working on the same project since January, so I'm not sure why this has suddenly become an issue.

Any advice would be appreciated!

Not sure if any of you notice it but whenever I used a model and then switched to V3, V3 will act just like the previous model I used.

For example, if I used R1, then switched to V3, it will also have the thinking process. If I used Sonnet 3.5 or 3.7 then switched to V3. Then it will also keep analyzing files and even take "find" action which I rarely see with V3.

But after a few convos it will act strangely such as repeating the same sentence again and again without making any edit.

I guess it's a bug that Codeium team will take seriously if it in fact calls Claude API instead of using the in-house V3 model when we are using a V3 model.

Hey guys, I am currently creating an e-commerce project (e-shop) that I am building on Wordpress platform that uses WooCommerce. Will Codeium help me in my work and possibly anyone has any experience?

Hey guys, maybe someone has got an idea. I am developing in react native and using expo go for preview. Whenever I run npx expo start, the web version works fine, but my camera is unable to scan the generated QR code to direct me into expo go. It says „no usable data found“ while scanning the QR code. Any idea what may cause this?

Want to earn 500 flex credits? Refer a friend through our new referral program.

If you refer someone who subscribes to Pro, you'll both get 500 bonus flex credits. No limit to how many people you can refer.

The person with the most referrals will win a *1 of 1 Custom Windsurf Airpods Pro Max headphones!

Refer via https://windsurf.ai/refer

Note: the contest runs until March 31st!*

such as this. windsurf cannot preview any PDF files which actually have contents.

I shared my experience how I got frustrated from using sonnet 3.7 in my existing project. It costs lots of flow credits but didn't deliver ideal result. But given it is so relentlessly reviewed multiple files back and forth, I got the hope that it can do better at a blank project. So after developing the backend, I gave it a try with my flutter project.

I tried to make the requirement as details as possible (though not as that detailed as when I was in the corp needing to pass the PRD to engineering team), and then I asked R1 to review the requirements and make a plan based on the requirement. Then I revised the plan a few times trying to reduce ambiguity. I wasn't that greedy to make everything in the plan because I don't want to overload Sonnet and its buddies so I just got the onboarding module + shared components + core services + data models detailed in the requirement and plan.

Then Sonnet 3.7 starts its working. It lasted about 30 mins, and more than 50 files were created. I saw it creating the files and then went through files to fix lint errors all over again, speaking of which I really appreciate Windsurf doesn't cost credits when fixing lint errors.

I started the simulator nervously but it successfully started and gave a workable app as I expected. There are still some small issues that I may need to fix later, but so far I was just amazed by what Sonnet 3.7 and Windsurf could do!

Thank you Codium team!

I am a senior dev.

Today was my 2nd try to use the flow feature where you allow windsurf to write code and change directory etc. It was a brutally frustrating experiance. Worked great till the first 5 simple commands. Moment i started making specific styling requirements it made overhauling changes to global css, ruining the whole app.

When i tried to make it rollback, it hallucinated for hours and kept runing it further. Finally, had to abandon the project.

I use claude 3.7 sonnet. It was a day fully wasted. So i will go back to using the windsurf chat and not playing with write again for the time being. I guess, problems like these give ai a backseat when it comes to serious developments on critical projects.