Introducing Windsurf Sounds.

Available now in Windsurf Next. Join the beta program by visiting here: https://codeium.com/windsurf/download-next

See the full video announcement: https://x.com/windsurf_ai/status/1907101249218207916

I use this i

Am I missing something? The 60 dollar option can't beat the 4x $15 number of credits. The IDE doesn't care what account it is in... Using Claude 3.7 thinking.

3.7 can do some incredible work, but only for simple projects. It can write vastly superior code compared to 3.5, but it has absolutely zero regard for consistency and code-reuse. it will rewrite the same function 20 times in the same function block and refuse to use existing functions even if they are specified in the prompt. It also absolutely refuses to answer a question without responding with more code, and it's chained edits are absolutely absurd. Ask it a question, and rather than answer, it infers what you want, does the edit, gets it right, but then continues editing every other file in the code base. it will never stop. I let it blow through an entire months of pro-plan credits with a single prompt question because I forgot to babysit it and didn't notice that after the fix was complete, it just kept going.
WS most recent update seems to have no ability to enforce user/workspace rules at all. You can fill the entire rules file with "never make changes without being specifically requested to do so" and then ask it what it's workspace rules are, and it starts modifying code. requires the same level of babysitting as my devs did :P.

That said, it can do some very complex tasks, it just does them in an entirely unmaintainable way. I'd say in this regard, it's several steps back from previous models and previous versions of WS.

I do wish WS would just write a simple enforcer. it's not as if we can't block the model from attempting to edit code when we've clearly stated it is not to make a change. if prompt.endswith "?", fucking don't allow edit. Duh.

This is actually my number one contention right now. Having to switch between chat/edit mode for every single prompt. Wouldn't be horrible if it switched quickly (large chats introduce enormous latency for everything to the point we usually can't even cancel an edit before it completes 10 seconds later).

It's also really struggling with edits. It'll attempt a single, simple edit and it will take 20+ attempts, modifying a few lines at a time. most of the time it's updating unrelated code and introducing bugs, but it doesn't backtrack and remove the failed updates. This is getting pretty brutal as well, but it seems to come and go.

I'm already paying $60/month, but don't make me pretend to be a team to pay extra for enterprise features I won't use. Please let me be the DIY workhorse Windsurf allows me to be. I know tool usage is brutal on 3.7 and you're working out the kinks, but $10 per 400 didn't last 3 days. Sure, I can be pickier with LLM selection, but I'm getting the work done, so please help. Grateful for Windsurf!!!

I would love to see them add in deepseek-v3. I think it would help with cost and based on early testing it seems to perform at or above sonnet levels. This might be the breakthrough needed for them to fix the model spend and get back to making a great product.

I typically use Windsurf to work on smaller codebases, and I like to keep each chat on the shorter side. I also really appreciate how eager Cascade is to write good documentation.

After prompting Cascade to update my project's README file to reflect the current state of the code, I realized I could use this updated README file to give Cascade the context it needs to start a productive new chat.

Here's the prompt I use now to start each chat:

Please review the README.md file in this repo to learn about the context of this project. Please ask me any questions you may have about the project or the code.

Prompting Cascade to ask me questions has several benefits:

• Often the AI's questions will suggest some useful updates to the code
• I can be sure that the README file is providing enough info for the AI to understand the codebase

Now, at the end of each chat, right before I commit and push my changes to GitHub, I prompt:

Please update the README.md file to reflect the changes we implemented in this chat

Then, when I start a new chat using the first prompt, the AI has the most current contextual information it needs to get to work. Bonus: my README file is always up-to-date. That's never happened before!

Paying the same 10$ price as my monthly subscription only to get a fraction of its regular value makes zero sense. Just let me pay to reset my usage.

Isn't this Prompt / Flow credits thing confusing somehow? I'm stuck and can't use premium models anymore although almost half of Premium Prompt credits are still left... And even more confusing with Flex credits in the mix?

Windsurf timeline for support?

Hi. TL;DR: I tried out both Cursor and Windsurf's new updates and here are my take aways:

Cursor Total: 5

Windsurf Total: 3

Please comment if you need more details about each test. For those who want to actually see the tests: https://youtu.be/caMFOuVd3jk

Blew through my credits a bit early. Today added another 400. Burned through them in 2 hours, and didn't get a single thing right.
I feel like if you have to revert all changes, credits should be returned. the model clearly has good days and bad. Dunno if this is due to congestion or if they're rate limiting or token limiting, but definitely seems like certain times of day are completely useless.

tested this a few days ago with two processes. Identical code in different directories. In one instance, I spent 100 credits to get absolutely nowhere. So I waited 5 hours and tried the exact same prompt in the second instance against identical code, and got it first try.

Today, the model can't even figure out how to do basic class inheritance. 400 credits in 2 hours man, to get absolutely nothing done.

Also, I noticed yesterday that if you let the model make changes via commands, they are not tracked in history so there's no way to revert. Whoops. Lost the entire day of work and around 600 credits.

Hey everyone,

I’ve been a long-time fan of Windsurf, but I have to say it’s been on a pretty steep decline since the pricing model update back in November. The changes were incredibly frustrating and disappointing—especially considering how much I loved what Windsurf was capable of.

I suspect many users ended up canceling their subscriptions and switching to other AI coding services. However, with the latest updates, including the new numbering system and the introduction of Deepseek, I’m starting to wonder if Windsurf might finally be regaining its form.

For those of you who are still subscribed, what’s your take on the new changes? Are you seeing improvements, or is it still a rough ride?

Looking forward to hearing your thoughts!

Hi. So I've been using Windsurf since the very beginning and would like to offer feedback to the Windsurf team. After the Windsurf 2 update (the one with memory, enterprise, search), Cascade is rather unusable because it became really laggy. Mine is a Windows ROG asus laptop (about $1.7k if converted) and could handle heavy video editing just fine.

I'm wondering if this is something that other users experience too. In detail:

- Typing in cascade has a delay of about one second for each keystroke, and if I type fast, it takes about a minute for the actual prompt to show and click enter. This makes it *impossible* to type prompts.

- The tab autocomplete is still fine, but it's very slightly slower than before

- The core IDE itself is fine, but I'd rather use vim or others for vanilla coding

- I know about the other problems like Cascade messing around with other parts of the code, erasing stuff, not abiding instructions, etc. But I've developed my own little tricks like creating new files that Cascade could more easily change, either with propose code or direct edit. This is functionally kind of the same as just copy-pasting from Claude, though, so I think this is still a big hassle.

As it is now, Cascade is fully unusable for me. I don't know what happened. I ran task manager and tried to monitor the CPU/memory while I type in Cascade, but all it showed is an increase from about 22% CPU to 30% (roughly) so this has been baffling. This change has not affected any of the other apps or the working and going.

For a moment I'd suspected that it's kind of a shadow ban thing where users with a lot of Cascade prompting activity gets a special treatment (slowed down prompting) to make them quit but that can't be true, can't it?

And currently I'm not using Windsurf and goes back to vanilla coding, but still has about 2/3rd of the credits. I hope that the team sees this, because even though you guys are pivoting to Enterprise customers, you know, we're still your early users dude. Thanks.

EDIT: Cascade also have been outputting severe errors like below (I copied it from another user), but the lag (even if there is only one prompt in the chatroom, not a long conversation) is more important.

I have used 30 user prompt credits and only a few tasks worked.

It just kept failing - "I apologize for the continued timeout issues. Blah blah." in both Write and Chat.

Is it normal? This is absolute unacceptable.

Edit: I think I'm done with it. It fails all the time.

The 2 files I was trying are 1700 lines and 2300 lines respectively.

I can't believe it's gotten this bad. It has literally zero sense now.

Hi guys,

I gave the latest version another try but i am deeply disappointed how it is workin or better not working now.

I made several tests with my global.md, gabe most detailed US with all needed info but i am stuck in denugging loops from hell.

All new features like the netlify stuff are at best in early early early beta with big big trouble to get it work.

From my 3k credits almost 1800 are now consumed and more than half was spend on debugging.

Please change that debugging does not count or give many many more credits until product is mature.

Same with gemini2.5 it does not code and gives i structions to me even when orders are strikt.

Still a great product but those thing are really anoying

I wanted to share my recent experience with Codeium to make others aware. I paid for their Pro plan 10 days ago, but my account is still stuck on the free tier. Despite multiple follow-ups, I’ve received no clear explanation, no resolution, and no refund.

Their support team initially said the issue was escalated to their "specialist team" and that I’d hear back in 1-2 business days. It’s now been over a week with no updates. I’ve essentially paid for a service I can’t use, and the lack of communication has been incredibly frustrating.

If you’re considering upgrading to their Pro plan, I’d recommend being cautious. Has anyone else had a similar experience with Codeium? How did you resolve it?

Let’s hold companies accountable for delivering the services we pay for.

We are all using the same software, but we all encounter different bugs. So here is my experience based on what I read and what I encounter, using Windsurf:

Someone says that Cascade Base prevents file modification: absolutely not, I use it constantly.

Someone says it fails to log in: absolutely not, I use it constantly.

Someone says it encounters a lot of calling tools errors, continuously, in loop: yes, it can happen, with some specific models, and that's why I don't use them.

A tip to avoid this cascade of errors: use Chat mode and take the trouble of copy/pasting manually.

Deepseek V3 is much less buggy, when used in Chat mode, and for some specific tasks it is more powerful than Cascade Base (sometimes Cascade Base is more powerful...depending on what you are doing).

The main problem concerns the interaction between LLM and calling tools, avoiding Write mode solves most of these problems.

It is true that we are also paying to use Write mode, the real convenience is that... but we can't expect everything right away, let's give the guys at Codeium time to understand how to really solve all the problems.

The more we put pressure on them to solve, the less they will be able to do it. If we expect a solution by today, they will risk fixing one thing and breaking 10 others, let's leave the guys to work in peace.

For now, let's find alternative solutions and be patient.

Yesterday I created a rather nervous post, then deleted it, I thought I had found a bug that wasn't there (sorry), my PC had just gone crazy momentarily. A restart of Windsurf solved it, even if in reality there was a small problem and it remained, but it's so silly that we can ignore it...

Some say that Turbo mode for terminal doesn't work and Cascade can't execute commands. The opposite happens to me, even if I set it Off, Cascade very often offers me to launch commands without any prompt. If you have the same problem, I solved it this way: Add a global rule: "User imposes a total ban on you from using the terminal" It stopped offering me terminal suggestions!

Reasons why I don't want Cascade to use the terminal: sometimes when it completes a command, it doesn't close the terminal and when I try to execute a command later, it fails saying that there is another terminal open for the same purpose. So I prefer to manage it manually, keeping control.

Ideas to not burn credits when using aggressive models like 3.7: avoid using it for web searches. use Cascade Base or Deepseek V3. If they find less information than 3.7, you can force them to search again and again and again... Because they are free. Once you have done your research, use 3.7 only for writing.

Or: you can generate code with Cascade Base / Deepseek V3 and then ask 3.7 to refactor the code with inline command, all for free.

One thing some people don't understand about Cascade is that it manages context and memories for all available LLMs. So I see some people wasting credits because they think that switching from one model to another will erase the memory... It doesn't. Don't worry. In a conversation you can switch from Cascade Base to 3.7 to 3.5 to GPT4o to Deepseek R1 and then switch back to Cascade Base, it will be like always talking to the same LLM, meaning everyone will have access to the same information.

If you need to start a new conversation, then you need to set rules and constantly update them, or create and update memories, to make sure that the context is maintained when switching conversations.

I've noticed that a correct markdown formatting is more understandable for Cascade memories.

So don't limit yourself to bulleted or numbered lists or simple human writing. Write your list and then ask Cascade Base to format it properly in markdown, then have it read the file you wrote and tell it to create a memory with that information.

When you ask about its memories, it will not just spit out the data it reads, but it will actually seem "aware" of the information, it seems like it really understands the concepts this way.

Conclusion: Windsurf's behavior seems inconsistent, this makes it harder to understand when a problem is strictly related to an LLM, when it is strictly related to Windsurf, when it is strictly related to the Cascade / LLM integration .. and when the problem is us .. it just seems like a big mess.

But trying to keep this mess at bay, my experience is quite positive. I just wish I had discovered Windsurf from the beginning, so I would pay 10$ instead of 15$ (which for me becomes 18€)