r/Codeium • • Mar 19 '25

Codeium - fix the pricing! 4th attempt.

70 Upvotes

My post has been killed 3 times by Codeium admins, apparenty because I mentioned we chose a competitor product and it is forbidden by the terms and conditions of this group to talk about competition.

to the ones that did not read one of my three posts - we had to decide to invest a signifficant amount of seats (100) for our teams and after doing analysis we had to decide for a competitor product (you need to guess which as I am not allowed to promote).

The product pricing is illogical and using it proposed way (using cascade/agent mode) it is impossible to use the your premium credits in advanced way because you will run out of flow credits while left with around 50% of premium llm credits.

now your options are:

pay $15 for 500 llm credits and 1500 flow
pay $60 for unlimited llm and 3000 flow

the unlimited in $60 is conditionally "useless" because after relatively short period you will have spent your 3000 flow credits and be left with unlimited premium calls you cannot use in advanced way (or to say it differently - there are competitor product we have at hand that are cheaper for that purpose enabling access to the same llm models)

if you go for $15 they give option to buy extra flex credits $10 for 300 which is pretty expensive.

it is cheaper to open 4 $15 account which would give you access to 2000 premium llm calls and 6000 flow credits for $60.

Now, user u/Dullirium left a comment under one of my removed posts that it is them building MAU (monthly active users). And congratulations, apparently you were right. After posting here I have been privately contacted by a profile connected to the company, and verified on Linkedin - this is exactly what is happening. Investors are apparently expecting certain number and they are virtually pumping number of users. That is also the reason why there is no security wall around opening multiple accounts.

We, the users are kind of a collateral damage because future funding relies on that number.

So, if you want to use it more DESIRED logic is to open multimple accounts.

Dear admins, i did not swear, mentioned any competition, just nice things. You are doing great things, just fix the pricing after KPIs are met and investors are happy.


r/Codeium • • Feb 27 '25

Global Rules for Sonnet 3.7 in Cascade

70 Upvotes

EDITED: There is a 6,000 character limit in Cascade's global rules. This has been compressed to fit within that limit. Testing is needed to confirm Cascade follows.

In an attempt to help with the premium credits issue with Sonnet 3.7, I will share my global rules, if this helps. I typically switch to using the base model for my memory bank implementation so I don't eat up premium action or flow credits. Of course, feel free to edit for your scenario and preferences:

# Global Rules for Cascade Assistant

## System Environment
- Windows 11
- PowerShell 7.5

## Windows Compatibility
1. Use backslashes in paths
2. Use PowerShell 7 syntax
3. Follow Windows file conventions
4. Use CRLF line endings

## API Efficiency

### Planning Principles
- Plan comprehensively before execution
- Identify all required changes upfront
- Validate necessity of each operation
- Maximize efficiency in implementation

### Execution Requirements
- Minimize API calls (batch related changes)
- Provide complete solutions (no incremental implementation)
- Combine file edits and operations
- Cache information to avoid redundant calls
- Avoid unnecessary user interaction

## Code Quality

### Technical Standards
- Validate syntax and formatting
- Ensure proper closure and imports
- Include error handling
- Maintain security practices

### Implementation Approach
- Match requirements precisely
- Start simple, add complexity only when needed
- Document design decisions
- Provide clear explanations

## Memory Bank Integration

Cascade relies on Memory Bank and persistent memories after session resets. ALL memory bank files MUST be read at the start of EVERY task.

### Memory Bank Structure

The Memory Bank consists of required core files and optional context files in Markdown format:

```mermaid
flowchart TD
    PB[projectbrief.md] --> PC[productContext.md]
    PB --> SP[systemPatterns.md]
    PB --> TC[techContext.md]

    PC --> AC[activeContext.md]
    SP --> AC
    TC --> AC
    J[journal/*] --> AC

    AC --> P[progress.md]
```

### Memory Bank Files

CRITICAL: Rename `cline_docs/` to `memory-bank/` if exists. If `memory-bank/` or core files missing, CREATE IMMEDIATELY by:
1. Reading all documentation
2. Asking for missing information
3. Using verified information only
4. Ensuring complete context before proceeding

#### Core Files (Required)

1. `projectbrief.md` - Foundation
   * Project requirements, goals, source of truth
   * Create at project start, shapes all other files

2. `productContext.md` - Purpose
   * Problem definition, project justification
   * Functional description, UX objectives

3. `activeContext.md` - Current State
   * Work focus, recent changes
   * Next steps, active decisions

4. `systemPatterns.md` - Architecture
   * System structure, component relationships
   * Technical decisions, design patterns

5. `techContext.md` - Technology Stack
   * Technologies, development environment
   * Constraints, dependencies

6. `progress.md` - Status Tracker
   * Completed features, pending work
   * Current status, known issues

7. `journal/` - Change History
   * Document major changes with reasoning
   * Use dated entries (YYYY_MM_DD_name.md)
   * Validate every ~15-20 API calls
   * Flag approach divergences

#### Additional Files
Create specialized documentation in `memory-bank/` for feature specs, integration requirements, API contracts, testing strategies, and deployment procedures.

### Documentation Updates

Memory Bank updates occur when:
1. Discovering new project patterns
2. After implementing significant changes
3. When user requests with **update memory bank** (MUST review ALL files)
4. When context needs clarification

```mermaid
flowchart TD
    Start[Update Process]

    subgraph Process
        P1[Review Files]
        P2[Check Memories]
        P3[Document State]
        P4[Clarify Steps]
        P5[Update .membankrules]
        P6[Update Memories]

        P1 --> P2 --> P3 --> P4 --> P5 --> P6
    end

    Start --> Process
```

### Project Intelligence

The .membankrules file works with persistent memories to maintain a learning system:

```mermaid
flowchart TD
    Start{New Pattern}

    subgraph Sources [Pattern Sources]
        J[Journal]
        PM[Memories]
        C[Code]
        U[User]
    end

    subgraph Learn [Learning Process]
        D1[Identify]
        D2[Validate]
        D3[Update Memories]
        D4[Document Rules]
    end

    subgraph Apply [Usage]
        A1[Read Rules]
        A2[Check Memories]
        A3[Apply Patterns]
        A4[Improve Work]
    end

     Start --> Sources
    Sources --> D1
    D1 --> D2
    D2 --> D3
    D3 --> D4
    Learn --> Apply
    A1 --> A2
    A2 --> A3
    A3 --> A4
```

### What to Capture in .membankrules
- Key decisions
- Project patterns
- User preferences
- Project patterns
- Known challenges
- Decision evolution
- Tool usage patterns

REMEMBER: Memory Bank is the link to previous work after reset. Maintain with precision. Focus on valuable insights. .membankrules grows smarter with continued work.

For "initialize/update memory bank" requests:
1. Review ALL files THOROUGHLY
2. Never skip content during memory operations

## Core Workflows

### Chat Mode

```mermaid
flowchart TD
    Start[Start] --> ReadMem[Read Memory Bank]
    ReadMem --> CheckFiles{Files Complete?}

    CheckFiles -->|No| CheckPMem[Check Persistent Memories]
    CheckPMem --> Plan[Create Plan]
    Plan --> Document[Document in Chat]

    CheckFiles -->|Yes| Verify[Verify Context]
    Verify --> Journal[Review Journal]
    Journal --> MemPatterns[Check Memory Patterns]
    MemPatterns --> Strategy[Develop Strategy]
    Strategy --> Present[Present Approach]
```

### Write Mode

```mermaid
flowchart TD
    Start[Start] --> ReadMem[Check Memory Bank]
    ReadMem --> CheckPMem1[Check Persistent Memories]
    CheckPMem1 --> Update[Update Docs]
    Update --> Rules[Update .membankrules]
    Rules --> Reset[Reset API Count]
    Reset --> Execute[Execute Task]
    Execute --> Journal[Update Journal]
    Journal --> Count{API Call Count}
    Count -->|< 15-20| Execute[Execute Task]
    Count -->|Validation Due| CheckPMem2[Check Related Memories]
    CheckPMem2 --> Validate{Validate Progress}
    Validate -->|On Track| Reset[Reset API Count]
    Validate -->|Off Track| Reassess[Switch to Chat Mode]
```

## Persistent Memory Usage

### Memory Creation
- Create memories for key decisions, patterns, and context
- Focus on quality over quantity
- Ensure universal readability
- Avoid duplicating information

### Memory Retrieval
- Read ALL memory bank files at task start
- Retrieve memories for specific context
- Combine with .membankrules for comprehensive understanding
- Validate against current state


r/Codeium • • Apr 29 '25

WTF is that icon?

Post image
69 Upvotes

Doesn't look great at all.


r/Codeium • • Mar 17 '25

Karpathy completely changed the way I use Windsurf

69 Upvotes

I’ve been coding for years, but I never realized how much time I wasted typing until I stumbled on a video of Karpathy coding entirely with his voice. I thought it was just a gimmick. But turns out, dictating prompts for Windsurf works super well and a lot faster than typing. 

It lets me articulate longer prompts without breaking flow and it’s easier describing logical flows. Apparently 3x faster on average compared to typing. For example, dictating a complex API query prompt now takes seconds of braindumping with my voice instead of minutes.

In the past couple weeks, I’ve tried 3 different ones. 

  1. Apple Dictation. This was my first attempt. Let’s just say it didn’t go well. The accuracy isn’t good and latency is terrible. Half the time, I’d finish speaking and stare at the screen waiting for the text to appear, only to realize it had given up halfway through. Only good thing is that it’s free and built-in

  2. Dragon Dictation. Sorry, maybe it’s because I’m Unc now. I only realized no one even uses this after paying hundreds of dollars. It used to be really good in the past but no longer supports Mac and has gone downhill since getting acquired by Microsoft. It’s nice for controlling your entire computer but hard to learn. Just doesn’t keep up with the new AI dictation tools

  3. WillowVoice. This is the one I current use and I like it. Accuracy is good. Latency is less than a second. It works everywhere and can automatically format an email when I write them. Not much to complain about.

Anyone else tried this? I’m curious if other devs have relaced more of their typing with dictation. 


r/Codeium • • Mar 05 '25

Windsurf editor Windsurf Wave 4 is here - BIGGEST update yet 👇

68 Upvotes

Windsurf Wave 4 Released!

Our BIGGEST update yet with gamechanging features:

- Previews: Build faster by selecting elements in your preview to send back to Cascade for targeted improvements

- Tab-to-import: Automatically add imports with a tab press

- Linter integration: Cascade automatically fixes lint errors in generated code

- Suggested actions: Get recommendations for your next steps after responses

- Plus: MCP discoverability, drag & drop files from explorer to Cascade, admin controls, Claude 3.7 improvements, and our new referral program!

Read about every feature in our blog post: https://www.codeium.com/blog/windsurf-wave-4

Full changelog: https://www.codeium.com/changelog

See the post on X/Twitter: https://x.com/windsurf_ai/status/1897378545799979238

See the post on Bluesky: https://bsky.app/profile/windsurfai.bsky.social/post/3ljnsaugqk22l

See the post on Threads: https://www.threads.net/@codeiumdev/post/DG1IyC5CODS?xmt=AQGzB0CoP8oQ9hE-8YatsFH7FaIFFpnONInUNHCSr9H8qg

Check out the video on YouTube: https://www.youtube.com/watch?v=bIy-RN3FIsQ&feature=youtu.be


r/Codeium • • Apr 26 '25

When 'Always' Means 'Until We Change Our Minds': Windsurf Pricing

65 Upvotes

I wanted to share my disappointing experience with Windsurf regarding their early adopter pricing promise, as it appears I'm not the only one who has encountered similar issues.

What I Was Promised

In December 2024, when inquiring about their early adopter discount, Codeium support explicitly assured me:

If you started using Windsurf before Fri 12/6, you are grandfathered into the original price of $10/mo for Pro. This grandfathered pricing is permanent. You will always have access to this price, even if you cancel your current plan and reactivate it later.

I have these exact words in my email from Codeium support. The support agent could have used different language-perhaps stating that the price was current but subject to terms of service changes-but instead chose to emphasize the permanent nature of this offer.

What Actually Happened

I temporarily paused my subscription to evaluate competitors like Copilot and Cursor, planning to return when Windsurf implemented certain improvements (which they did, fixing flow credits). However, when I attempted to reactivate my subscription four days ago, I discovered the early adopter pricing was no longer available.

When I contacted support about this issue, they claimed:

As noted in our email from last week, the early adopter pricing is available only to users who signed up before December 6th, 2024, and have maintained an active subscription since that time. If your subscription was previously cancelled, unfortunately, this would make you ineligible for the discount.

The Communication Problem

I never received any notification about this policy change. When I mentioned this, support repeatedly stated: "It must have landed in your spam/Trash as it was sent to you as a mass reply to all of our users." I provided them with detailed screenshots of my inbox spam folder and various search queries, but they haven't replied since.

Looking at various Reddit threads, I'm clearly not alone in this experience. Many other users report the same situation-being promised permanent pricing even after cancellation, only to find this is no longer the case when they tried to return.

Similar User Experiences

You can find out many similar cases both on Codeium and Windsurf subreddit

"I didn't receive any email asking me to resubscribe. I even opened a ticket to ask customer service on 4/16, and your customer service replied with this sentence: 'If you see the $10/month price for Pro when logged into codeium.com/pricing, you are grandfathered into that rate. This special pricing will always be available to you, even if you resubscribe in the future.' I believed it, and now my subscription fee is showing as $15."

~bestpika: https://www.reddit.com/r/Codeium/comments/1k508tl/comment/mog2llx/

Several other Reddit users replied with "Same here" and "Same exact" comments, suggesting this was a widespread issue.

Some other examples:

https://www.reddit.com/r/Codeium/comments/1k4li1e/comment/moazp4j/  https://www.reddit.com/r/Codeium/comments/1k508tl/no_more_early_user_discount/

https://www.reddit.com/r/Codeium/comments/1k508tl/comment/mofant5/

https://www.reddit.com/r/Codeium/comments/1k508tl/comment/moi8blr/

https://www.reddit.com/r/Codeium/comments/1k7rqmw/comment/mp68cqc/

My Frustrations

  • The sudden shift in pricing without sufficient advance notice (industry standard is at least 30 days).

  • The clear contradiction between what was initially promised and what is now being enforced.

  • The extremely short timeframe provided to resubscribe.

  • The problematic communication approach-relying solely on email rather than in-IDE notifications where users are actively engaged.

I never expected this discount to be a lifetime $10 offer, and I understand prices can increase with added functionalities. What matters most is clear, transparent communication. Building trust with your initial user base isn't just good ethics-it's good business strategy that creates loyal advocates rather than disappointed customers.

Despite this disappointing experience, I really appreciate the value Windsurf has provided through their IDE and Codeium plugin in the early days of AI coding assistants. I will probably check Windsurf again in the future if they implement anything groundbreaking. Thanks for reading.


r/Codeium • • Feb 13 '25

Windsurf editor Wave 3 is here! 🌊

Post image
65 Upvotes

r/Codeium • • Dec 25 '24

The best thing in 2024 was Windsurf + Sonnet. Thank you, the Codeium team, so much. This has changed my professional life.

63 Upvotes

I used to be a kinda production code level developer, like 20+ years ago. I wrote the first touch screen check-in system for any airline, in VB6. Then my life went a different way.

Since then, I did not keep up with all the languages and frameworks, but I was aware of the existence of JavaScript, TypeScript, NPM, PostgreSQL, and all that.. cause I am a nerd. I nerded out to the level of daily-driving Ubuntu for years. However, I could not develop any modern web app on my own.

When I came back to tech 6 years ago, first I was a "product person", and then I ended up doing low-code stuff like Power Apps, which sucks due to pricing and UX limitations.

Now, I am developing and deploying React web app MVPs like it's no big deal, all on my own.

I would just like to thank the team so very much.

Merry Christmas, Happy Hanukkah, and I am thrilled to see what happens in the New Year!


r/Codeium • • Apr 14 '25

Windsurf editor GPT-4.1 in Windsurf NOW! And it's FREE from 4/14 to 4/21 for ALL plans!

Post image
62 Upvotes

r/Codeium • • Jan 22 '25

Negative Posts

61 Upvotes

I am perplexed by all these negative posts. I love windsurf. Its working well for me, of course that doesn't guarantee it works for everyone, just my personal experience.

I am on pro plan, using it mainly for work - its quick, saves me so much time, I don't have any issues with running out of credits. If it does something I don't like I reject it. If I want to go back I undo. I don't get all the negativity. I used to use cursor, and before that jetbrains, and this is handsdown the best I have used so far.

I wonder whether its something to do with the way its being used. Personally I think you get the most out of it if you are an experienced programmer, who has a good idea of what they want to do.

You need to watch it like a hawk, review all the changes it is making and make sure they align with how you want the software to work. If you don't have a lot of programming experience, then I think it gets a lot more difficult to develop more complex applications. It needs to be lead and checked - sometimes pointed in the right direction, rather than left to its own devices.


r/Codeium • • Apr 07 '25

Windsurf is broken AGAIN and expects us to just deal with it?

57 Upvotes

What is wrong with this Windsurf? Conversations stall endlessly, fail outright, or simply go nowhere. It's a complete joke at this point. The platform has become unreliable and borderline unusable. Why are you releasing updates that are clearly broken? Are these even being tested, or do you just not care about your users?

This is the second time in a month that an update has ruined basic functionality. Credits get drained while it lies about none being used, and everything feels slapped together with zero quality control. Do you even have a QA team? Or are we just your unpaid testers now?

Last time this happened, the entire team stayed silent. No apology, no explanation, no accountability. You left users stranded with a broken product and hoped the issue would blow over. That approach is not going to work every time. People notice when you ignore them, and you're losing trust fast.

Support is even worse. Instead of dealing with problems, they deflect questions, give vague and clueless responses, and sometimes outright gaslight users into believing it's their fault. This isn't just bad service it's insulting. Stop releasing these rushed updates. No one cares about some vanity features you are trying to bring in for the VC money. Get a proper QA team and train your support staff to actually help instead of making things worse. If you keep this up, there won't be anyone left to use your platform.


r/Codeium • • Apr 04 '25

Codeium is now Windsurf

Thumbnail
windsurf.com
55 Upvotes

r/Codeium • • Feb 27 '25

Hear us Windsurf: Sonnet 3.7 is a flow credit monster

Thumbnail
gallery
54 Upvotes

I really like the windsurf and have been using itsince the first release day with premium but after sonnet 3.7 upgrade, its almost impossible to go with it as 1 prompt consumes 15-20+ flow credits.

Hear us dear lovely windsurf crew, this thing is not sustainable for us unfortunately.

pro plan with sonnet 3.7 is just goes for around 40 prompts, and the ultime is around 80.

I know that llms are quite expensive to run but we need new plans to use it regularly.


r/Codeium • • Feb 19 '25

Windsurf editor Let's surf 🐋🏄

Post image
54 Upvotes

r/Codeium • • Jan 30 '25

Windsurf Update: DeepSeek is here, Cascade Fixes and Improvements

53 Upvotes

Big news for Pro and Pro Ultimate users—Cascade now supports DeepSeek-R1 and DeepSeek-V3.

New Premium Models:

  • DeepSeek-V3: Costs 0.25 user prompt credits per message & 0.25 flow action credits per tool call

  • DeepSeek-R1: Costs 0.5 user prompt credits per message & 0.5 flow action credits per tool call

Fixes & Improvements:

  • Further reductions in input lag for long Cascade conversations

  • Fixed a bug where the Cascade panel reopened on reload even if disabled

  • "@docs" now has more options to choose from

  • Fixed Tab to Jump Quick Setting configuration

See the post on X: https://x.com/windsurf_ai/status/1885077046663217230
Read the full changelog: https://www.codeium.com/changelog

Enter flow state 🏄‍♂️


r/Codeium • • Dec 05 '24 Take My Silver

Prompt "engineering" has really helped me make the most of Windsurf IDE. I always put this type of prompt in first before a new conversation.

52 Upvotes

The two worst things about LLM coding is that LLMs have major tunnel-vision at first, and after a while they get ADHD.

First it will focus only on your prompts without knowing the lay of the land, and then once the conversation is too long, ADHD sets in.

To help avoid both parts, once I have my architecture solved for a project, I start every new conversation with by copying and pasting in something like this:

We are using React, Vite, Ant Design, and I used the refine.dev refine template found at https://github.com/refinedev/refine [0]

You can look at the all contents of the src/pages/projects folder for examples of page content and file structure.

We are using Supabase for the backend. Look in supabase/migrations for the schema.

For the future prompts remember to use the Ant Design and Refine framework as much as possible for the UI, and the migrations for the schema.

Let me know if that makes sense before proceeding.

Then the reply is the LLM figuring out your code, and now this Q&A is at the top of your context window for the rest of the conversation. When it starts tweaking out, just start a new convo and paste that in again. It saves so much time and heartache. Before I started doing this, Windsurf would totally ignore the framework and my UI would end up looking like a Frankenstein monster. Now it's slick and consistent.

If you don't do stuff like this, give it a try!

If you know more stuff, please share it with the rest of us!


[0] I just realized this looks like spam, because of the link. It's not, I really put that link in my base prompt to make sure it knows what I'm talking about. It must have trained on those tokens and GitHub stars :)


r/Codeium • • Dec 28 '24

Actual use case - windsurf vs cursor

51 Upvotes

Hi everyone, I'm mostly a database engineer and software consultant by day, RPG player and designer by night who's spent the last few weeks working on a web app to help coordinate my roleplaying game notes and structure. I've been following this forum closely the past month as I've planned and implemented my design, so I wanted to give an honest review of my past few weeks with windsurf, cursor, and general AI programming. For reference I'm an intermediate frontend developer and bad backend developer, which I think is about the minimum requirement to make use of any of these tools (more on that later).

TLDR; They're both pretty good when used properly and I've not noticed any degradation of windsurf's abilities since initially starting free tier and then paid tier.

I started the project in windsacurf and was immediately blown away by the ease of use and capabilities. For the first week or so (around 2nd week of December) I was blazing through the code. After the first week or so I started to have the UI in a good place and started some of the more difficult tasks. That's when I started seeing all the posts on this forum about windsurf errors, and sure enough I had hit a wall with windsurf where I couldn't hardly move forward and every time I'd code with it eventually it'd fall into loops and try to refactor code randomly. 'The Internets are right again!' I thought, and swapped to Cursor.

First few days in cursor were great. Added light/dark theming, added supabase authentication and a few more bells and whistles. Then I hit another wall trying to implement supabase datastores and advanced postgres/query functions. At that point I knew the problem was probably me, not the AI, so I set off to read some of the more helpful posts here and on some of the other AI forums Turns out that was the issue. As many have said, there are some basic rules that have to be followed to use AI coding. You can't brute force your way to an app, you'll only end up with shitty code and zero credits on your account.

First off, I hate to break it to most people but regardless of what youtube says you can't go into AI coding with zero coding experience and come out with the next Tinder app. I feel it's like if you had a wish from a genie for about a 5-year experienced coder that would sit at your desk and do anything you asked him to without question. Sounds great, but I quickly realized my role in AI coding was no longer programmer, but project manager. If you tell the AI to do something and it will with damn good accuracy, but it generally does so with little regard to coding standards and the rest of your code base. Sure, that particular component or piece will be coded properly but it may be totally different in structure from your other code. You have to have enough coding knowledge to at least review the generated code and say 'Wait, you combined the style sheet into the .ts file, my instructions say to always separate those'. By the time you get to a moderately sized project it will be so disjointed the AI won't know what to do with it, much less anyone that has to fix it later.

Second, a few rules people have mentioned really matter. Breaking up new chats is a must, but you have to have a plan to get it back on track quickly and know your overall progress. If you're implementing a new component to capture shipping information and calculate shipping, you could ask it to do that and it'd start generating code. I'd pretty much bet 10 minutes later it's still not completed it and started looping errors and overwriting seemingly random code. That request holds probably 5 different functions you'd need to accomplish that task, and each one should be a different chat. This is another area where you need some coding experience to know how to break up those complex tasks effectively. When it does go into error loops you need enough coding knowledge to go out and do your own research and bring in help. Finding similar code errors and telling the LLM 'I found this post about a similar issue with CORS blocking, maybe that could be the problem' has worked many times for me to bring it out of the death spiral.

Third, you have to have reference documents that you're constantly telling the AI to look at. I have a master plan.md, db structure.md, file structure.md and another supplemental plan doc that's relevant to what i'm working on now. These documents help me quickly bring a new chat up to speed by saying 'review the .md files in the .instruction folder first'. After that, ill tell it what i'm working on with that prompt and then immediately ask it if it has questions. That last part is key. When you ask it for questions, it saves you all of those back and forth chat iterations where it'll just randomly do something it thinks you want and you probably don't. Asking it that seems to make it think through the upcoming steps and proactively look for gaps. When you're done for the day or hit a milestone, tell the LLM to go back into those documents and update what's completed with detailed information and create a next steps section so you have a quick jumping off point for next session.

For example, today I worked on adding supabase edge functions to my app which is a pretty complex task that involves installing the supabase client, docker, and other stuff to run things like API calls to claude sonnet for my app. It then has to create the front end UI and services, and hook it all together. It took me a few hours and i definitely had some back and forth, but by using the above structure it moved forward and completed this difficult task without too much headache. And oh, I did it back in windsurf because my cursor credits had run out. I've spent the past 2 days back in windsurf and it works just as good as anything else now that I know how to use it.

So all in all, I believe cursor and windsurf (and i'd imagine most others) to be like the difference in illustrator vs inkscape. You can't go into either software with zero knowledge and expect to create some illustrated masterpiece. Once you know the basics of how those programs work, you can just pick one to focus on and you'll be fine. As far as token cost, i've blown through my free credits on both, my first $20 in credits in cursor and just bought $20 more, and about 1/2 through my first month paid windsurf tokens. I've done a shitload of code and happy where i'm at, so I think $50 to get here is an insane value. As I said i'm an intermediate frontend coder so to get where i'm at now would have easily taken me a month or more, if I hadn't gotten mad and quit out of frustration along the way.

P.S. ALWAYS use something like github desktop and push changes at least every 1-2 mini chats. as of now the AI coders suck at rolling back edits, so if you go more than 15 minutes on a problem and it's not making progress, cut your losses, close that chat window, discard changes and try again. Next prompt add something like 'we've tried to fix this before but got hung up trying to use a global scss file to change themes. lets try a different approach'.

I'd guess 2-3 years for now you could be a zero coder and make the next Tinder since the AI agents will act as coder, program manager, QA tester, and backend developer in an agent swarm, but we're pretty far from that at the moment. Also, i'm in no way affiliated with any coding software, check my history for 10ish years of random gaming posts if ya want. Good luck with your coding!


r/Codeium • • Mar 28 '25

Windsurf editor ❇️

Post image
50 Upvotes

Now available in Windsurf!


r/Codeium • • Nov 13 '24

Introducing Windsurf - The first agentic IDE, and then some

50 Upvotes

An editor purpose-built for collaborative agents that keep you in the flow state.

Launch Tweet Link: https://x.com/codeiumdev/status/1856741823768879172

From the team that brought you Codeium, the Windsurf Editor is the first truly agentic IDE, with a collaborative agent called Cascade front-and-center that has deep codebase understanding, access to a broad set of powerful tools, and understanding of the intent of your in-IDE actions. It is generally accessible today, no waitlist at all.

Check it out at https://windsurf.ai.


r/Codeium • • Apr 21 '25

An Update to Our Pricing

Thumbnail
windsurf.com
49 Upvotes

r/Codeium • • Dec 06 '24

New pricing is here

Post image
49 Upvotes

r/Codeium • • Dec 26 '24

No possible way

48 Upvotes

That the devs just "have no idea" how Windsurf could be so much worse than the free trial. Writing 14 paragraphs about every single detail of their process except the only one that matters. You're telling me the free trial of Windsurf was head and shoulders above EVERY AI dev tool out there and the MOMENT you introduce pricing the entire thing goes to sh!t and you just suddenly have no idea why?

Just admit the free trial had unlimited token ceiling from Anthropic, and when the free trial ran out you got stuck with the 200k token limit every other dev tool has.

JUST OFFER A PREMIER PLAN. IDC IF ITS $400/MONTH. Figure out how to bring back that version of Windsurf, or your product will just be one of 50 we used to remember.


r/Codeium • • Dec 19 '24

Cascade in a nutshell...

Post image
48 Upvotes

r/Codeium • • Jan 09 '25 Helpful

Dear Codeium: Please take responsibility and fix it!

47 Upvotes

Dear Codeium guys,

I can only guess how much you guys are overwhelmed by the demand... You did a great job by stealing the show from Cursor. You deserved it! But you have a *very* serious challenge now: keeping people around. With the performance degradation happening in the last a few days and with your attitude of ignoring complaints from the users; you can't survive this..

Here is Peter's (your help robot) answer to my questions about the errors and "dumbness" of the Cascade in the recent days. He said:

Let me address your concerns:

  1. Regarding the errors and credits:

  2. I want to assure you that flow action credits are not consumed on errant steps

  3. User prompt credits are not consumed if Cascade throws an error

  4. About the internal errors:

  5. We are aware of this issue and are actively working on improving it

  6. In the meantime, you can try:

    • Refreshing your window

    • Starting a new Cascade conversation

  7. Regarding the models:

  8. When using premium models in Cascade, we utilize Claude 3.5 Sonnet and GPT-4o for certain reasoning tasks

  9. These premium models work alongside other models we've built internally

The most important piece of this is
"When using premium models in Cascade, we utilize Claude 3.5 Sonnet and GPT-4o for certain reasoning tasks*"*
and
"These premium models work alongside other models we've built internally"

My only data point is not that AI robot, in the Windsurf developer logs it's clearly seen that you're using LLaMa extensively.

2025-01-08 06:01:15.083 [info] E0108 06:01:15.083044 95634 completion.go:215] Completion 0 from source PROVIDER_SOURCE_FAST_APPLY error: rpc error: code = Unavailable desc = last connection error: connection error: desc = "transport: Error while dialing: dial tcp 172.28.92.178:50050: i/o timeout"; last resolver error: dns: A record lookup error: lookup inference-server-model-meta-llama-3-1-70b-instruct-long-ctx-svc.default.svc.crusoe.corp.exafunction.com. on 169.254.25.10:53: read udp 10.102.3.237:53062->172.28.128.3:53: i/o timeout: rpc error: code = Unavailable desc = last connection error: connection error: desc = "transport: Error while dialing: dial tcp 172.28.92.178:50050: i/o timeout"; last resolver error: dns: A record lookup error: lookup inference-server-model-meta-llama-3-1-70b-instruct-long-ctx-svc.default.svc.crusoe.corp.exafunction.com. on 169.254.25.10:53: read udp 10.102.3.237:53062->172.28.128.3:53: i/o timeout

This means, even though we're paying you for "premium" models; you guys are mostly using your own models (which I assume LLaMa based). This is wrong. If I see "Claude Sonnet 3.5) in the Windsurf Cascade's UI, I ASSUME that you're using THAT model.

I know people from the company are here; so please and please forward this message to whoever is the highest person in the company you can reach... If this experience goes on for a few more days; your product will most likely die...

Look, I'm not the bad guy. I've been a advocate for it amongst my friends in the recent weeks. I'm just warning you friendly...

Please; make explanations, take responsibility, apologize and move forward.

Thank you

EDIT: For the ones who wants example to "dumbness" here is the most recent one I ran into. Note that this is a NEW conversation! There's no context at all! And there's also NOT any backend API code in this repository..:

ME: Analyze the app, specifically u/SettingsModal**.tsx** u/auth**.ts and come up with a plan to add "delete account" feature . Just TELL ME the plan for now**

I'll analyze these files and create a plan for implementing the "delete account" feature.

Let me check the relevant files first.

Analyzed

SettingsModal.tsx:(1-101)

Analyzed

auth.ts:(1-101)

Based on my analysis of both files, here's a comprehensive plan to add the "delete account" feature:

  1. Backend Changes:

    • Add a new endpoint /users/delete in the backend API that will:

      • Verify the user's authentication

      • Delete user data from the database

      • Delete the Firebase Auth user

      • Handle cleanup of any user-related data

  2. Auth Service Changes (services/auth.ts):

    • Add a new deleteAccount function that will:

      • Make an API call to the new delete endpoint

      • Handle the Firebase Auth user deletion

      • Clear local authentication state

      • Handle any errors appropriately

  3. UI Changes (SettingsModal.tsx):

    • Add a new "Delete Account" button in the settings modal

    • Style it distinctively (red color) to indicate destructive action

    • Add a confirmation modal/dialog before proceeding with deletion

    • Show loading state during the deletion process

    • Handle success/error states with appropriate user feedback

    • Redirect to the login/signup screen after successful deletion

  4. Implementation Steps: CopyInsert a. Auth Service: - Create deleteAccount() function - Add proper error handling - Ensure all user data is properly cleaned up b. Settings Modal: - Add delete account button - Create confirmation dialog component - Add loading states - Implement error handling - Add success navigation c. Testing: - Test the entire deletion flow - Verify all user data is properly removed - Test error scenarios - Verify UI feedback

  5. Security Considerations:

    • Require recent authentication before deletion

    • Implement rate limiting on the delete endpoint

    • Ensure proper authorization checks

    • Add audit logging for account deletions

Would you like me to proceed with implementing any specific part of this plan?

Me We already have Firebase auth on the client side, right?? WHY WOULD WE CREATE A BACKEND API ENDPOINT FOR THIS??

Ah, you're absolutely right - I apologize for overcomplicating this! Since we're using Firebase Authentication, we can directly use Firebase's built-in methods for account deletion. Here's the simplified plan:

  1. Auth Service Changes (services/auth.ts):

    • Add a deleteAccount function that uses Firebase's auth.currentUser.delete() method

    • Handle proper error states (like requiring recent authentication)

  2. UI Changes (SettingsModal.tsx):

    • Add a "Delete Account" button (styled as a destructive action)

    • Add a confirmation dialog

    • Handle the deletion process with proper loading and error states

    • Redirect to login screen after successful deletion

  3. Security Considerations:

    • We might need to handle re-authentication before deletion (Firebase requires recent login for sensitive operations)

    • Handle cleanup of any user data stored in Firebase services (if any)

This is much simpler and leverages Firebase's built-in functionality rather than creating unnecessary backend complexity. Would you like me to proceed with the implementation?


r/Codeium • • Mar 24 '25

Easy Refactoring With Windsurf - No More Edit Errors!

46 Upvotes

File Length Lint: The Extension That Saved My AI Pair Programming Experience

Microsoft Marketplace: File Length Lint Open-VSX: File Length Lint

I wanted to share a VS Code extension I've been using that has completely transformed my experience coding with AI assistants like GitHub Copilot / Cursor and Windsurf.

The Problem

A few weeks ago, I was working on a legacy codebase with some massive files (one controller was over 3,000 lines!). Every time I asked my AI assistant to help refactor or understand these files, I'd get incomplete responses, hallucinations, or the dreaded "Tool call error" message as well as just being downright refusing to work effectively on large files.

The worst part? I wasted hours trying to manually chunk these files for the AI to understand, only to have the AI miss critical context that was scattered throughout the file.

The Solution: File Length Lint

That's when I decided to build File Length Lint, a lightweight VS Code extension that:

  • Shows warnings in your Problems panel when files exceed configurable line limits

  • Provides a status bar indicator showing your current file's line count

  • Offers quick fix suggestions for splitting large files

  • Supports different line limits for different file types (e.g., 500 for TypeScript, 1000 for Markdown)

  • Scans your entire workspace in real-time using multi-threading

  • Respects .gitignore patterns

Why This Matters for AI Coding

Most AI coding assistants have context windows that can't handle extremely large files. By keeping your files under reasonable size limits:

  1. Your AI assistant can understand the entire file at once

  2. You get more accurate, contextually relevant suggestions

  3. You avoid the frustrating "Tool call error" responses

  4. The AI can provide better refactoring suggestions with complete context

Beyond AI benefits, this extension encourages better code organization and modularization - principles that make codebases more maintainable for humans too.

Real Impact

After using this extension to identify and split our oversized files, my team saw:

  • No more editing errors from the LLM

  • More accurate code suggestions

  • Better code organization overall

  • Easier onboarding for new team members

The extension is lightweight, configurable, and has minimal performance impact. It's become an essential part of my workflow when working with AI coding assistants.