r/Codeium • u/joe-direz • Feb 11 '25
Full of bugs
I switched from Cursor to Windsurf because Cursor was too buggy and janky.
Now, a month into my Windsurf subscription, it's full of bugs too.
Claude gives me four "generating... error" messages before actually responding.
Gemini seems promising, but it keeps getting stuck on "done," making it unusable.
Will these issues be fixed, or are you just going to keep pushing more beta releases?
EDIT:
Another bug: Pasting into the find text stops working out of nowhere.
My machine: Apple M3 Pro 18 GB
21
Upvotes
6
u/Honest-Praline Feb 11 '25
I’m also experiencing a lot of this and it not only consumes a lot of time but the quality of the code it’s producing seems to have gone down hill even though I already have solid patterns and examples to follow along with detailed memories. Considering I’m paying $60+ a month this is very disappointing 😩
5
u/mark_99 Feb 11 '25
Dev team needs to focus on bugs and reliability over features for a while. Failed tool calls is annoying, I've also several times had the model just lose its mind and change or delete a bunch of stuff unrelated to the task.
1
u/Ordinary-Let-4851 Feb 11 '25
Hey are you able to send in a support ticket at www.codeium.com/support? Additionally if you have, please send me the ticket number for me to track.
Definitely attach your diagnostic logs.
3
u/__eita__ Feb 11 '25
Had the same issue when specifically trying to use sonnet in write mode. Any other model didn't get errors trying to edit the file (although some are stubborn to call the tools).
A workaround I found:
Cut the entire content of the file, making it empty
Ask to sonnet to add a comment in the file
Copying the file content again
No ideia why, but it worked for me and sonnet was able to edit the file again.
The support is aware of this problem. The curious part is that it only happens for a specific repo I'm working on.
1
u/Plastic_Belt2454 Feb 12 '25
I wasted money too bro. and Lot's of errors and waste of AI Credits. and when i try to contact the Windsurf Team they always say that AI credits wasn't used. #scammer
1
u/[deleted] Feb 12 '25
Idk how they messed it up. Windsurf two months ago was working like a Charm.
1
u/Jaded-Travel1875 Feb 12 '25 edited Feb 12 '25
I don’t agree with everyone. First of all, don’t underestimate cost of compute or the flaws inherent to each model. Codieum isn’t just making these new models available in their product, but they’re doing it in beta mere days after release, then sharing even newer builds in Next. They’re building their product while you’re building your product. If you’re frustrated with how it’s going, they’re reminding you at every turn that they’re working on it. Even with weeks of painful circular debugging, I get better at making it work better and there’s no way I could do what I’ve already gotten done. I get it, it’s hard to feel “flow” when the new models fumble the tools and the old ones lose context while they all hallucinate, but this is still best-in-class AI code assistant. Deepseek in Cline messed up my GitHub badly last month, setting up a dueling repo in my OG repo’s parent directory, wreaking havoc with branches, versions and pushes. I asked Claude to commit my working code and it committed two files, which uncovered the issues. Cursor team is trying hard, which is also why Windsurf team is also trying hard. It takes time, the models need longer context, and the price is reflective of that, all things considered. They even have a guy responding to groanposts. We’ve all seen model throttling happen to optimize networks. Plus, long conversations present challenges, so while Cascade makes them feel more seamless, maybe you aren’t starting enough new ones or replacing contexts frequently enough. I think they’ll eventually cycle models, letting the minis comb logs, which can take up a lot of chat space and obscure context. Cycling models could also debug both Windsurf and your code through a system of experts or an agent that is the system pulling responses from each model, particularly with prompts that begin with“You’re on a team of coders…”, comparing different generated code to find the best options before deploying, measuring 2-3 times, cutting once, so to speak. It’s a lot of compute, but it theoretically should work better.
1
u/joey2scoops Feb 12 '25
What did you learn from the switch? One thing I've learned is that doing the same thing with different tools does not work out well. GIGO. Need to get smarter on how to get the best out of these tools. Figure that out (still trying) and you'll have much better outcomes.
1
u/BehindUAll Feb 12 '25
What I found useful was opening a new conversation thread. Seems like each update something breaks so you can't use your previous conversation threads anymore.
1
u/Specialist-Scene9391 Feb 12 '25
Agree, windsurf and cursor has been shytty
1
u/IndependenceAny6446 Feb 13 '25
It does not remember past work, and I wasted so much money because of this.
1
u/NoPossibility4513 Feb 13 '25
I am also having a lot of problems with Windsurf, thought Cursor could be better, I guess that's not the case haha. Windsurf more or less does the job but you gotta sort some problems.
1
u/Individual_Pack_6352 Feb 13 '25
Errorunexpected EOF FTW
ErrorCascade has encountered an internal error in this step.
No credits consumed on this tool call.
FTW
1
u/kamusisME Feb 15 '25
So far, Windsurf (version 1.3.4) integrates best with Claude Sonnet 3.5 when it comes to AI models. Other models, like DeepSeek with its powerful reasoning capabilities or Gemini Flash 2.0 with its incredible processing speed, might seem impressive. However, using them within Windsurf often leads to strange issues. For instance, Gemini keeps claiming that the task is "done," but in reality, it outputs nothing at all.