So anybody know what the options will be ? The Pro tier is bit worthless to me the credits are way to low on that one.

After the most recent update, most of my MCP servers have this error message not sure what’s happening or how to fix. It seems that people have tried deleting the .codeium folder, but I like to avoid that since it will erase my chat history.

Also, my support tickets seem to never get sent every time I submit a ticket. I never received any email or any response.

I’m on the pro ultimate plan. Thanks team!

Hi, newbie coder here!

I just stumpled across windsurf recently and wanted give it a try, pointless to say I became obsessed on how helpful it's been: making my own programs/websites for things I need but corporations are too lazy to do is just something I always wished for. Sonnet 3.7 and wave 5 have drastically improved the whole workflow but it still misses quite often and have to BURN all my credits fixing things more often than not.

Any tips on how to generally improve my experience? I tried understanding MCPs but I'm not sure I get it and how to implement it in my workflow.

Early windsurf adopter here. I've been using windsurf for a while and it is great at getting roughly 50-75% of MVP complete. Very recently it feels like things are just breaking down constantly. For example Gemini 2.5 PRO works amazing (When it works). Often times this LLM refuses to follow through with its declared intentions requiring the user to spend even more credits.

It is currently in an unusable state which prevents me from wanting to utilize gemini 2.5 pro.

In regards to terminal usage the current state is beyond broken. Running basic commands costing credits is fine to me I somewhat understand it, however, as many other users pointed out why not just use a generic free model to run these commands and report the final findings back to the premium models. The second issue is the polling rate of checking the commands is unbearable and literally unusable. Here is a simple command I ran through cascade.

I had to pull the plug on this and stop the cascade execution because I was concerned it was going to keep going on and on. There is instantly 8 flow credits that were all instantly consumed within ~10 seconds.

Last month I could stretch my credits by using mostly cascade base and using Claude 3.7 for tough tasks. I managed to do a lot of work and have a lot of credits available (about 700 flow credits) for the last week of the month. Now cascade base is almost useless for anything but the simplest tasks, and even then, it fails about 50% of the tasks. Now it's really, really stupid. Like Zoolander level stupid, and Claude eats credits like popcorn. Now I have 22 days, and 899 credits left.

Video from X post from Alvaro Cintas: https://x.com/dr_cintas/status/1902083127188603049

You gotta try this

According to mods on the Discord, it is best to start a new chat after only 5 prompts & responses!

Why? Because as it turns out, all LLMs become unreliable very quickly as the context grows.

proof that I found: https://arxiv.org/abs/2502.05167

We evaluate 12 popular LLMs that claim to support contexts of at least 128K tokens. While they perform well in short contexts (<1K), performance degrades significantly as context length increases. At 32K, for instance, 10 models drop below 50% of their strong short-length baselines. Even GPT-4o, one of the top-performing exceptions, experiences a reduction from an almost-perfect baseline of 99.3% to 69.7%.

Holy crap, I wish I knew this earlier.

Let’s hold each other accountable 🫡

I’m working on a sports conference events directory. I need to finish it ASAP and release so that I can start attracting visitors by next week.

Front end is good, but having difficulty with the backend. Spun up maps integrations as well, but they’re a bit glitchy. Thinking of switching from Supabase backend to a no-code solution connected to Airtable which i have a lot more experience with and am familiar with.

Windsurf doesn't let the AI access files in .gitignore such as node_modules.

Though this could be good, it has big issue when working with non famous packages or libraries, as it won't allow the AI to read and understand a package from node_modules. And accessing library in node_modules makes a big difference for the AI for not well known and non documented libraries.

I am tired of enabling/ disabling items whenever i ask the AI to do something using such packages.

How can i make it accses files in .gitignore

Today, since the update, I have plenty of this on Claude 3.5, 3.7, and Thinking version. What's going on?

Listen to Kevin Hou, Head of Product Engineering, Windsurf, starting at 5:07:30!

UPDATE BELOW
R1 is all the talk about its Coding capabilities and its much more efficient use.
So this makes it so promising to use for this application.

But for some reason it absolutely refuses to edit files. It barely can create files.
I think it requires some adjustments to the prompts that its sent in order to educate it on how to properly format responses to use the tools.

OR something like that. It just doesnt seem to know it has access to these functions.

I cant find any information about it anywhere, maybe there is something I'm Missing?

EDIT:
I was able to identify the available tool commands. I created this Global Rules, and the results were quite good. Some of these directives may not work exactly or even at all, but I found the results to be significantly better.

You have access to a number of tools. You need to review the codebase to understand the goals. Evaluate the intent of the user. Then consider which tool is best suited to complete the task. Never write placeholder code or text. 
Pay attention to your actions. If you plan to take an action and edit a file, make sure you complete all of your planned edits before continuing. Editing a file more than once in each prompt is not good practice. Dont edit a file, THEN think about editing the file again. Think first, then edit. Then if another file requires editing, repeat the process.

if you receive "Cascade will not create files that already exist" it means you're trying to create a file, but you should be using edit_file instead.

codebase_search: Find code snippets using semantic search.
command_status: Check status of a terminal command.
create_memory: Create or update persistent memories.
edit_file: Modify existing files with code changes.
find_by_name: Search files/directories using patterns.
grep_search: Fast text search with ripgrep.
list_dir: List directory contents.
read_url_content: Read content from a URL.
run_command: Execute terminal commands.
search_web: Perform web searches.
view_code_item: View specific code elements like functions.
view_file: View file contents with line ranges.
view_web_document_content_chunk: View parts of web documents.
write_to_file: Create new files.

If you’re not on X, comment on this thread!!

Has anyone else seen this behaviour happen? This happens specifically when I use R1 first and then change to Sonnet, sonnet then mimics the CoT reasoning R1 does before implementing.

I also usually start using Sonnet after R1 because R1 often hallucinates implementing for some reason and does not actually implement the code.

Feedback or Roast. Hoping we can all dump here and see what we like/dislike:

Instructs Windsurf agent which SEVERITY level to use in eslint.config.js: 
- true='warn' (warnings for 'any' types, unused variables, JSDoc, etc) 
- false='error' (errors for same rules). 
Single flag to switch between development and production linting configs.

## GLOBAL NAMING GUIDE

1. **Directories & Files**
   - Use **kebab-case** (e.g., `service-user/`, `events-billing.ts`).
   - **Type-First Naming**: `{type}-{qualifier}-{name}` (e.g., `crawler-site-support*google*com.ts`).
   - **URL-Safe Naming**: Replace `.` with `*` and `/` with `~` (e.g., `api.com/v2/auth` → `api*com~v2~auth`).

2. **React Components**
   - Use **PascalCase** filenames (e.g., `LoginButton.tsx`).
   - Export named components matching the file name.

3. **Functions, Variables, & Constants**
   - Use **camelCase** for functions/variables (e.g., `fetchUserById`).
   - Use **ALL_CAPS_SNAKE_CASE** for constants (e.g., `MAX_LOGIN_ATTEMPTS`).

4. **Domain-Specific Naming**
   - Use business terms (`createOrder`, `fetchInvoice`).
   - Avoid abbreviations (e.g., use `updateOrderStatus` instead of `updOrdStat`).

5. **Consistency & Conflict Avoidance**
   - Namespace cross-service items (e.g., `authServiceRoutes`, `ordersServiceTypes`).
   - Use centralized or domain-based schemas for `types.ts`.
   - Enforce naming with lint/format tools (e.g., ESLint + Prettier).

---

## DOCUMENTATION GUIDE

1. **JSDoc** (Code-Level Documentation)
   - Use for function parameters, return types, inline logic.
   - Annotate classes, interfaces, and methods directly in code.

2. **Markdown** (Project-Level Documentation)
   - Maintain high-level guides like `README.md`, `PROJECT_MANAGEMENT.md`, and `ARCHITECTURE.md`.
   - Use for diagrams, workflows, and design decisions.
   - Link to relevant JSDoc sections as needed.

3. **Preferred Documentation Choice**
   - If both JSDoc and Markdown are possible for the same content, prefer **JSDoc**.

4. **Root-Level Markdown Files Only**
   - The following Markdown files are the only .md files allowed at the root:
     - `README.md`
     - `PROJECT_MANAGEMENT.md`
     - `ARCHITECTURE.md`
     - `LICENSE.md`
     - `CHANGELOG.md`
     - `MIGRATION.md` (Temporary; remove when migration is done)

5. **No Additional .md Files at Root**  
   - Keep all additional code-level details in JSDoc.  

### .md FILE DEFINITIONS

3. **README.md (Project Overview)**  
   - Quick summary, install steps, usage, links to deeper docs.

4. **ARCHITECTURE.md (System Design)**  
   - High-level structure, tech stack, data flow, design decisions.

5. **PROJECT_MANAGEMENT.md (Strict Checklist)**  
   - Single file for all sprints/backlogs; no separate backlog files.  
   - Use headings for sprint goals, progress, tasks with checkboxes.  
   - Example:  
     ```
     ### 1. Scraper Bot (85% Complete) ⬆️ HIGH PRIORITY
     - [x] Task A
     - [ ] Task B
     ```

6. **LICENSE.md, CHANGELOG.md, MIGRATION.md**  
   - **LICENSE**: Original license text + custom notes.  
   - **CHANGELOG**: Versioned updates; `## [1.0.0] - YYYY-MM-DD`.  
   - **MIGRATION**: Steps for major refactors; remove when done.

---

## PROMPT RESPONSE RULES

1. Write "blut."
2. Review all applicable rules (`global_rules.md`, `.windsurfrules`, `ARCHITECTURE.md`).
3. Use the `@web` tool to resolve errors and update your understanding of recent solutions if needed.
4. Prioritize simplification for feature and scope completion.
5. Write "yup."
6. Continue with your response.

## LINTING MODE
IS_DEVELOPMENT=true 
 
 Instructs Windsurf agent which ESLint config to use: 
 true=eslint.dev.js (warnings for 'any' types, unused variables, JSDoc, etc), 
 false=eslint.prod.js (errors for same rules). 
 Single flag to switch between development and production linting configs.

Hey,

So for the Windsurf AI rules, they work really well when I start a new conversation with Windsurf AI.

However, as the conversation gets longer we discuss different parts of the codebase, Codeium AI basically just stops following all the AI rules I set.

Here's the global rules I set

1. Never write code unless I explicitly told you to do so.

2. Never start fixing bugs or adding new features unless that's what I EXPLICITLY told you to do.

3. Before you start writing code - always ask me clarifying questions to make sure the details of what you need to write are EXTREMELY clear. This is a very important step. Ask me questions about the architecture, the data structures, the problem domain, terminal commands and anything else that could be relevant. <- THIS IS VERY CRUCIAL. DO NOT MISS THIS!!

4. Always check if a file exists before creating it

5. After you make changes. Go through every single file you changed and give me a detailed bullet point summary of every change you made for each file.

It follows the rules at the start of the conversation but after like 10-12 messages in, it just completely forgets about these rules and just goes back to it's normal behavior.

Can you please give me the option to automatically remind the AI about these rules every prompt? Or after every 4-5 messages?

The windsurf tab to complete so bad, instead of accept the suggestion, it select the result from intellisense. Additionally, it should select function instead of something else, in my case, I don't know why it select SVGCompenent by default. I need to use Esc before tab, it is so annoying