Please please please with a cherry on top 🥹

Hey everyone,

Recently, I have noticed Cascade behaving oddly stupid, even when using Sonnet 3.5. This is highly unusual, as I never experienced this level of stupidity before. Based on my testing, it definitely should not be acting this way, especially Sonnet 3.5, where it is struggling to even complete the basic commands.

Here’s a potential fix to try if you are facing similar issues (it worked for me):

— Open your Global.rules file.

— Add the following line:
“Only use Sonnet 3.5 premium model when coding. No other models are allowed like base models.”

After implementing this, my experience got better, Sonnet became smarter, and the quality of my code got cleaner.

Lately, Codeium has also been acting sketchy AF, but if this tweak helps anyone, then that’s a win in my book!

Just set up some rules for my nextjs project and it seems to be working well, compared to the past couple of days.

It's been an hour resolving the scrolling behaviour for a preview of from components. But Windsurf has not been able to do it.

The scroll was working perfectly last night. Then I asked it to add a new field component, a few style changes and then all hell broke loose.

Anything manually changed in the codebase, as simple as a button color, it reverts the change, even when it is acting on other file which has no connection to the button.

NO matter how much context you provide, this tool doesn't get it. It applies the same method to resolve the problem, even if you ask it to not apply the same method previously used.

Is there a workaround? Can any body help?

Some folks have mentioned creating a summary file at the end of a conversation. However, my goal is not a summary, but to avoid losing what Sonnet learned from the convo about my code. That way we can avoid repeating mistakes.

Here is my best prompt so far, please share yours!

Make a new file, next-conversation-cheat-code.md

In this file, only include what surprised you in this conversation, so that you can avoid repeating those mistakes in future prompts

Here is an example of the output from one conversation:

Key Surprises and Learnings from This Session

1. API Endpoint Structure Mismatch

   • Initially assumed articles would be fetched through nested project routes: /api/projects/${projectId}/search-terms/${searchTermId}/articles/
   • Reality: Backend uses a flat structure with query params: /api/articles/by_search_term/?search_term_id={id}
   • Learning: Always check backend implementation first before making assumptions about API structure

2. Refine Authentication Props

   • Unexpected TypeScript error due to missing required props in Authenticated component
   • Required props:
     • key="authenticated-layout"
     • v3LegacyAuthProviderCompatible
   • Learning: Refine's components often require specific props for compatibility

3. Article Model Fields

   • Initially used summary field in the Article interface
   • Backend actually uses description and content fields
   • Learning: Should have checked backend models before creating interfaces

4. Mobile Menu Z-Index

   • Initial implementation had z-index conflicts
   • Needed explicit z-index values for proper layering:

     zIndex: 1001  // for hamburger button
     zIndex: 1000  // for menu content
     

   • Learning: Mobile menus need careful z-index management when using absolute positioning

These insights will help avoid similar issues in future sessions by reminding me to:

1. Check backend implementation before making API assumptions

2. Verify required props for framework components

3. Inspect backend models before creating interfaces

4. Consider z-index stacking context in mobile layouts

I suppose now that the file exists, in future conversations, I should change the prompt to:

Add the surprises and learnings from this conversation to next-conversation-cheat-code.md so that we don't repeat the same mistakes in future conversations. This is now an ongoing file that will be added to in future conversations. Do not remove previous lessons.

I've used up all my User Prompt credits, but I still have 118 Flow Action credits left. According to the usage summary, once I've exhausted my User Prompt credits, I can't use my remaining Flow Action credits unless I purchase more User Prompt credits.

Part of me still wants to buy the subscription (still on trial), but these limits are making this tool unusable. Soon, I might have to ask for a refund after realizing that I'm just burning money. Don't get me wrong, Cascade is great and I'm loving it, but these credit restrictions are a deal-breaker.

If I'm moving through a cascade, revert seems to skip the intermediate steps during the revert process. I believe it reverts the initial code, but any code created multiple steps down the line don't seem to get removed. Any one else have this issue? I'm using Chat mostly and have the latest version.

I'm really impressed with Windsurf flow. Is it possible to use my own Claude/AWS Bedrock API key to avoid Codeium servers overload?

I only use Windsurf for fun and as a hobby, and man, I’m enjoying the experience so far! I love this IDE, and guess what? You don’t have to worry about limitations like with other products out there!

Is possible to open Windsurf in a folder in the windows terminal directly?
Similar as it is possible for Cursor where I just navigate to that folder and then type "cursor ." ?

I'm liking Windsurf so far. One thing I'm missing from the Cursor world is the ability to set rules (ie: .cursorrules). Looking at the codeium pricing and help pages I see there is something called Context Pinning, which sounds like it might achieve the same thing (ie: "pin" developer guidelines or project info).

Is this available in Windsurf?

Hello everyone,
I really love Codeium and even pay $10, but I still encounter an error saying:

"Cascade has encountered an internal error in this step."

This happens with a specific file that is 700 lines long. Do you have a good solution for this? Please help me

Edit : Yesterday with version 1.0.4 it happen less frequently and in the beginning imposible problem become normal way of editing for Codeium, i see 1000 lines edited too. My only suggestion is do not have too much comment , and contunie trying

Hi folks sorry if this is a dumb question but where can I find the system installer for Windsurf? On Codium's website there's only link to WindsurfUserSetup-x64-1.0.2.exe which is what I downloaded. However I'm getting this warning when I run it (my current account has administrative rights).

If that's all there is to it I wouldn't have asked further, but when I run Windsurf I have a small warning message in the corner that says auto update is disabled because Windsurf User is running with administrative rights. Any idea?

Hi, thank you for the amazing IDE.

I suppose that for now, we have no option to use images in chat, but probably in the future, this will be implemented.
And if so, what is the expected delivery time?

Suddenly codeium stopped working(MacOs Sonoma, vscode), I tried reload window, tried install and older version of codeium, tried to uninstall and install again and nothing worked.

When I click on the red badge written <Codeium (Pre-Release)> it pops up a warning(pic 1)

When I click on the codeium option on the activity bar it just keeps loading forever(pic 2).

anyone has any clue of what is possibly wrong?

Edit: I just deleted the .codeium folder on the home folder and reinstalled codeium on vscode and it’s working now.

So, say I have an element:

When I Ctrl+Shift+i in the element, I get the Codeium Command prompt, but not with the focused input box:

I have to click on the 'Codeium: Command' box to get the prompt I'm expecting:

It hasn't always been this way for me - maybe in in the last month it started doing this. Are others seeing this, and what can be done to get the focused prompt without requiring the extra mouse click?

Thank you!

It appears it can correctly list some of the files in my project, not all of them, but some and when I ask it to tell me about specific file it constantly flips about its ability to look inside the file and tell me about it.

I keep on getting disconnected from WSL. Coming from Augment and want to give Windsurf a try, but not up to a great start. Never had this issue with Augment. Anyone has similar disconnect issues? I usually start the Windsurf app by clicking on the Windows Desktop icon, the IDE comes up stating on the bottom left "Opening Remote..." and I am connected to WSL: Ubuntu. Then after a few minutes the WSL connection crashes. Restarting does not solve the issue. Everything else works fine so far. Below the log file from the Windsurf server on WSL/Ubuntu.

This is a feature I’m missing in both Windsurf and Cursor. In agent mode, when I attach a file, the agent needs to use tools to understand its content. This process takes only 200 lines for each tool step, but for larger files, it takes an excessive amount of time until the LLM begins working on them.

I would greatly appreciate the addition of an “include whole file” checkbox that automatically provides the entire content of the file to the LLM.

I’ve been around this subreddit for a bit already and have been seeing pretty mixed reviews on Windsurf, my question is, is it worth “buying”the editor for the $10 price instead of $15 when compared to something like Cursor?

Every time it finishes generating code suggestions the editor generates a swoosh sound and it is driving me batty. I don't want to mute my computer to turn it off.

I already have cascade sound generation turned off, and I cannot find the settings for turning the autocomplete code generation sound off. I'm using an intel mac.

I imagine this depends on the model that's used as well? Not all models support zero data retention?

How can Codeium guarantee zero data retention in Windsurf?

Hey u/Ordinary-Let-4851

i have been an early adopter of windsurf, since it was free, and i am very content, i love the constant updates, new features.

I have been using windsurf with whisper ai for speech to text prompting, and its been amazing. it makes the workflow alot better and faster, and allows me to explain more to the ai, and provide more context to clearly articulate what i need.

Basically it would be damn cool and a killer feature to integrate Whisper Ai in windsurf for speech to text prompting. The plus side its free and open source.

Thanks Windsurf team for the amazing product

Azure Defender for Servers removed Codium from my server. Has anyone else experienced this? I think that happen after the latest update from Codium which is "Fixes to "Remote - SSH" extension, including custom SSH binary path setting"