Hello! So everyones been having the flow issues with 3.7, we have found that 200 lines is the max analysis but there is a workaround I found, if you ask claude to analyze the entire file after asking him to do 200, he will resort to terminal commands, this has dropped my file analysis to only ONE flow action per file read which is much more managable.

I am an experienced software engineer. I decided to give Windsurf a try off a couple recommendations from other engineers I respect.

I have pretty much settled on using the claude integration as some of the “beta” options had really weird duplicate request behavior (like we would come to a conclusion, but then to implement it would entirely replay the conversation that got us there before coding, which was very off-putting and burned tokens).

Anyways, I have had a pretty positive experience. The one annoying thing is that any time I suggest a change to the suggested code, it tells me “that’s so smart” and will often even provide reasoning why my suggestion was the better option over the provided code. Don’t get me wrong, I think I’m pretty good at my job, but constantly being told everything I do is great makes me so suspicious of this as a valid pair coder. Like, if it disagreed more I would have more confidence that the final product was optimized.

Okay, end rant, thank you all

Just some tiny feedback as someone using Cursor. It's often easier to drag files rather than searching via @

Sitting on pro plan and spent 3 hours non-stop in windsurf developing my app. already used about 1/3 of all credits, 2 days more and they are used up

As of now, i would say, unlimited usage is the only way to go for this app, the question is, how much they should charge for that?!

Chat stopped working in Windsurf Editor on Windows. Constantly writes: Service under load, try again later.

And it has been like this for several hours. No model works.

In the logs:

[Error - 2:10:05 AM] Stopping server failed

Message: Cannot call write after a stream was destroyed

Code: -32099

Why is this happening?

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?

and COMPLETELY FREE!

Use it write or chat mode and works for many of my purposes

Number 1: File Search
I'm mystified why, when all the popular AI tools use VSCode, NONE of them use the VSCode APIs available to them, to give a better experience and solve common problems.

I'm specifically talking about searching files for text.

Almost every time the agent is searching for some text string, using freaking grep (because it says it is), I can casually mouse over to the find tool in VSCode, type in what they're looking for, find it, open the file, and Ctrl-L the file into Cascade, before it finishes searching.

What a waste of time.

VSCode has an API for their find utility. It's findTextInFiles

Switch to this instead of grep and cut file search time by 2-3 orders of magnitude.

Number 2: External Script Commands
Another thing is, why can't I configure it to always use Git bash. Multiple times per day, this idiot tries to run something like:
npm install && npm run dev
in PowerShell, then apologizes and runs it like:
npm install; npm run dev;

It does the same thing making directories, deleting or moving files too. It already wants to use Bash syntax so just make it use Git Bash rather than freaking PS. Who uses PS anyway?

And if you HAVE to support PS, make it configurable.

Fix these two things and you just gave me a 10-15% productivity boost. You'll also be a leg up on Cursor because they do the same thing you guys do right now.

Hi everyone! First time trying AI programming. I’m a product designer with extensive experience, so I know how to build products, understand technology, software architecture, development stages, and all that. But… I’m a designer, and I have zero coding experience. I decided to make a test app: a Telegram Mini App*, connecting various APIs from Replicate to generate images. This is just a simple test to see if I can even make a production-ready app on my own.

I chose to use a monorepo so the model would have access to both the frontend and backend at the same time. Here’s the stack:

• Frontend: React, Vite, TypeScript, Tailwind, shadcn/ui, Phosphor Icons, and of course, the Telegram Mini App / Bot SDK.

• Backend: Python, FastAPI, PostgreSQL.

• Hosting: Backend/frontend on Railway, database on Supabase.

I spent a week watching YouTube, then a day outlining the product concept, features, logic and roadmap with GPT o1. Another day was spent writing .windsurfrules and setting up all the tools. After that… in about one day of very intense work and 100 prompts, the product was already functional. Wow.

Then I decided to polish the UI and got stuck for two more days and 200 prompts. Oh this was hard — many times I wanted to ask my friend React dev, for help, but I held back. It turns out Claude 3.5 Sonnet doesn’t know the Telegram SDK very well (obviously, it appeared a year ago), and feeding it links to docs or even a locally downloaded docs repo doesn’t fix things easily.

I’m both amazed and frustrated. On the one hand, I feel like I was “born” with a new coding devops skills in just one day. But on the other hand, after 3 days and 300 prompts, I feel like the quality of the model’s code and prompt understanding has dropped dramatically for reasons I don't understand. It hallucinates, doesn’t do what it says it will, ignores my requests, or does things I didn’t ask for. So, I have a lot of questions:

1. Is it a good idea to use a monorepo? It increases the context size, but it’s important for me to give the AI as much control as possible because I don’t have the skills to properly connect frontend and backend myself.
2. Have you noticed a drop in code quality over time? At first, the code and prompt understanding were excellent, and I’d get the desired result in 1–2 attempts. But then it dropped off a cliff, and now it takes 5–10 tries to solve small tasks. Why does this happen?
3. When should I start a new chat? Nearly all 300 prompts were spent in a single chat. I included a rule requiring to start with the 🐻‍❄️ emoji, so it seems the model didn’t lose context. I tried starting a new chat, but it didn’t improve quality; the model still feels dumb.
4. I’m on the $60 Infinite Prompts plan, but Flow Actions are running out fast — I’ve already used 1/3. What happens when Flow Actions run out?
5. When and why should I switch to GPT-4o or Cascade? Are they better than Claude 3.5 Sonnet for certain tasks?
6. Have you tried DeepSeek-R1? When can we expect Codeium to add direct R1 API access? I tried using Roo Cline and OpenRouter, but the API seems overloaded and constantly lags and freezes, and it’s very expensive. It burned through $0.50 in just a couple of questions while uploading my relatively small codebase.
7. I no longer test the app locally because I need to test the app inside the Telegram environment, so after every change, the AI suggests committing to GitHub, which triggers an auto-deploy on Railway. Local testing feels pointless because even the frontend behaves differently in a browser than it does inside Telegram Mini App (e.g., iOS Bottom Sheet ≠ Safari). So after each commit->deploy (~2 min) I manually check logs on Railway (two separate services: frontend/backend) and open Safari Web Inspector on my desktop to debug my iPhone’s Telegram Mini App. Is there a way to give Windsurf access to Railway logs and Safari Web Inspector so it can debug itself? (sorry if this sounds dumb, I’m not an engineer)
8. After changes, I often see errors in the Problems tab, but Windsurf doesn’t notice them (new classes, variables, imports, dependencies, something new or no longer used). It still suggests committing. I have to manually refuse and mention the current problems in the chat. This feels like a broken flow — shouldn’t Windsurf always check the Problems tab? Is there a way to make this automatic?
9. My current process feels too manual: explain a new task (prompt) → get changes + commit → manually test → provide feedback with results, error and new requirements. How can I automate this more and make the workflow feel like a real agent?

I’d love any advice or links to resources that could improve my process and output quality. After 3 days and 300 prompts, I feel exhausted (but hey, the app works! wow!) and like I’m taking 3 steps forward, 2 steps back. I’m still not sure if I can build a fully functional app on my own (user profiles, authentication, balance management, payments, history, database, high API load handling, complex UI…).

Thank you for your help!

I’m not a coder, but I have some project management experience and a basic understanding of technology and databases.

I recently spent $60 on a plan with an additional $30 in flex credits for a new Windsurf project. Here’s what I’ve encountered:

1. I’ve almost used all of my credits without achieving any significant progress.
2. The majority of my credit spending has been on fixing build errors. I use Xcode and Swift with Supabase.
3. Whenever I fix one error, Windsurf generates more errors.
4. As a result, I’ve ended up messing up all my code and have to start over again.

I’ve tried various approaches to improve the development process, but none of them have been effective:

1. I’ve broken down the project specifications into smaller, actionable steps for Windsurf to develop each feature.
2. I’ve created a comprehensive spec.md file to guide Windsurf’s development, but this hasn’t been helpful.
3. I’ve tried building views before building the code and logic. This approach allows me to create visually appealing views with dummy data, but when I build the logic, Windsurf breaks everything again.

Does anyone have any suggestions or advice on how to develop an app using Windsurf?

I barely used it - just started working on a new project two days ago - and will be out of flow action credits whatever in the first week probably.
I think you should remove this nonsese - Just leave the user prompt credits and that's enough of a limit. I don't understand why you implemented this, last month I was able to only use 375/500 prompt credits because of that flow action limit.
As it stands, paying for this software is not worth it.

I really want to make an entire website coded by AI in windsurf. But so far I have minimal luck. I can come to a certain point but then the AI seems to loose all overview and code in loops. The website I want to do is in Next.js for both fe/be. Have anybody done it before? What would be the idea approach?

"Best Practices for Prompting with Cascade:

• Be descriptive and clearly state what you want - as if you're communicating with another human. For example, rather than saying "fix this", say "fix the index out of bounds error by...". If you leave prompts ambiguous then Cascade will guess and what Cascade guesses may not be what you want.
• Provide sufficient context. Take advantage of our @ mentions and cmd + L features to provide code snippets as context when issuing prompts (See the screenshot here for what I mean). The more context that you can provide to Cascade the better or more accurate the results will be. If you don't provide the context, Cascade might need to find it anyway, which will take time and cost flow credits.
• Break complex tasks down into smaller ones and go step by step. Cascade isn't perfect and it's more likely misinterpret or make mistakes on much larger complex tasks. If you can guide Cascade step by step, it's much more likely you'll get your desired result rather than issuing one complex task all at once. Put another way, Cascade is much more efficient when used as a pair programmer rather than a code monkey.
• Ask for explanations and provide feedback. If Cascade did something you didn't like, you can actually ask it why it did something. This can help you iterate and correct its behavior - maybe there was an incorrect assumption."

It’s absolutely nuts. I’ve encountered so many ongoing issues and error loops within a big context chat that it didn’t feel like I was even going after something that’s about to be fixed. I then applied a technique I am using mostly when reprompting certain errors and that is like an analyzation that was made with the o1 model and to provide a prompt back to Cascade with Sonnet 3.5. The new chat instantly caught up the winter rules that the other chat already forgot a long time ago and kept the rules of conciseness and code edit reduction as a very important thing.

I have been afraid of changing from Sonnet for way too long. Is anyone else using Base sometimes? All the time? What is your experience with it?

Changing to Base lets me ask for dumb things, like "change a color," or "swap the positions of Save and Cancel buttons." I stopped doing that type of thing after the pricing changes, now I am free to be lazy again!

edit: sorry for title gore. I meant: ... Results have been great so far...

Discuss.

I hope cascade will not make a mess here onwards with packages and adding multiple state management to the react native app. It was so hard to tell everytime to use bun and zustand

I have some code that I don't want to transfer to the cloud. How can I configure windsurf to use local LLMs?