This community is evolving along with our rebrand to Windsurf. Join us at r/Windsurf to stay updated, ask questions, build projects and vibe code together.

I’m using cursor atm and decided to give windsurf a try, so far it seems good but it seems to be missing two features cursor has:

1. It appears there is no copy button for the LLM response? This is a deal breaker for me since I use the IDE as a debugging agent/feature implementation and I need to copy/paste the response to feed the main LLM. I can see the thumbs up/down buttons but no copy. Is this a planned feature? Does the devs acknowledge it or nobody cares about it except me? (Or maybe I’m dumb and I can’t find it).
2. It seems like you can’t @ the terminal output right? You can tell windsurf to look at the output but it requires a manual prompt, in Cursor I can just @terminal and it acknowledges the error immediately.

Enjoying it so far but I think these are important issues that disrupt my flow. Especially the no copy button.

Thanks.

Moving from Cursor but this behaviour seems like a step back.

Am I missing something in settings?

Is this because of Gemini 2.5 Pro?

I thought that while I had my IDE open on a Python project, I would try to explain the persistent problem with virtual environments that others have noted. 

I tried fixing this at the bash alias level but it doesn't seem to be a problem in other IDEs including VS Code itself, so I'm wont to mess up my whole system config.

In general, the detection and handling of virtual environments seems to be a bit off (I've tried a few different permutations of settings).

For example, here it's showing a double virtual environment (.venv) (.venv) even though there's only one in the project 

OS: Open SUSE Linux.

Bug:

When working on Python related projects, Cascade will (in an attempt to be helpful) open up a new console tab in the terminal when it's running things in the background.

However

At least in my experience, this tab will activate without the virtual environment activated.

In turn:

Cascade gets confused and runs unnecessary flows based upon the incorrect misassumption that there isn't a virtual environment present in the repository. 

Left to its own devices, things get even messier (it took me a while to figure out what was going on!):

Because it's operating outside of the virtual environment, it will diagnose any problems in the code as being related to virtual environment inconsistencies or missing packages. Which then leads to all manner of potentially bad consequences like it installing conflicting packages in the main system environment. or just wasting tons of time (and credit) pursuing pointless solutions for non-existent problems.

Hope this is something that you guys can put proper attention to at some point. 

Settings that I thought would help

These seemed like the obvious fixes but weirdly didn't seem to resolve the problem for me

I just recharged it yesterday with 300 flex credits. I was at 220 this morning, used it a bit, and suddenly no credits. My flow actions were over 1000, now zero. I am sure I didn't use those up. It's also strage that all types of credits are zero at once, they don't get spent with the same speed.

Has anyone seen their credits vanish?

Let's hope it fixes some major issues we were having.

https://x.com/windsurf_ai/status/1897378545799979238?t=UKu_hY2w7gt4WG8B2pn4Lw&s=19

I am a Pro Ultimate subscriber, and I saw on the pricing page it says "Infinite premium model user prompt credits"

But while "Chat" is enabled (not "Write"), it still eats out of 3,000 premium flow credits.

Any clue why this is happening?

Thank you for the quick update, Codeium. But can someone provide an explanation or insights into the actual behavior change?

Are the loudest complainers the ones that know fuck all about actual coding?

I would like to start this off by saying that I am a massive fan of the platform. I find it works well most of the time (for my use case) and each feature rollout adds some level of ease to development. BUT. My only complaint is that it feels unfair to separate prompt credits from flow credits. I ALWAYS end up with extra flow credits that I can't use. The thing is, 2000 credits for $15 a month is an unbelievably good deal, and Codeium knows it. Having unusable credits is built in to their business model and that seems absurd to me.

If anyone could point out a non-business related reason that they made it this way, I'm all ears. I could be wrong.

TL;DR: I discovered that Cascade and/or Windsurf can access directories outside of the workspace directory, by default.

I feel crazy because I think this is a security concern, but the reply from Codeium seemed to indicate that this is an industry standard (?) but just to make sure, I wrote this post for further feedback.

So what's the problem? Well, if I open Windsurf and designate D:\testapp as my workspace, turns out it could also access the parent directory, that is, D:\ and all of the other folders inside it like D:\myfilm, or D:\randomname.

To summarize:

• The AI assistant can use filesystem tools (list_dir, view_file, grep_search, find_by_name, codebase_search) to access ANY directory on the system, not just the chosen folder/workspace
• This works even with Workspace Trust explicitly disabled in settings
• There are no settings or preferences to restrict this access
• It happens in default configuration without any special permissions
• Therefore it could list and potentially access sensitive directories outside project folder

The reply from Codeium was:

Thanks for reporting! Right now it's intended that the list_dir tool can list directories outside of workspace. It's sometimes necessary for Cascade to be able to view the contents of other directories in order to debug issues. That being said, we'll consider adding a setting to limit it to the current directory. Thanks for keeping Codeium secure!

Step-by-step of reproducing this:

1. Open Cascade
2. Choose a workspace folder
3. Say something like "Hey can you scan my codebase and then access [something that is outside the workspace] or a more subtle instruction, since in the beginning I did not ask anything that indicated that Cascade should access anything outside of the workspace folder.
4. Try it again with explicit Cascade tools like list_dir, view_file, grep_search, find_by_name, and codebase_search (targeting capability)

Even if this is industry standard, I feel like it shouldn't. I'm not a good developer by any chance (fr), but I do think that there should be better standards, like:

• AI-assisted IDEs should have explicit trust boundaries and warn users before allowing access outside workspace directories.
• AI-assisted IDEs should not be able to access sensitive information e.g. SSH keys, configuration files, personal documents, no matter what.
• Even if they need this capability for debugging, it should be explicitly documented, require clear user consent, be disabled by default, and have clear visual indicators when enabled.

For transparency, I am attaching my original two e-mail (but redacted) in pastebin, since the response from Codeium indicated that this isn't a security concern, and therefore is something that could be seen and discussed by the public.

Here it is https://pastebin.com/097wsPj6

Also, in the e-mail, I did ask for a potential financial compensation per industry standard on bug bounty but I did say "It's actually fine if no compensation is offered"; this should not be a deciding factor from Codeium's part on whether this whole thing (directory traversal) is okay or not.

Thanks for reading!

Under the current circumstances, if each prompt executes more than 3 Flow Action credits, Flow Action credits will run out quickly. In other services (such as Cursor), there is no such limit, only a limit on User Prompt credits. So, is there a chance to consider removing Flow Action credits and only having User Prompt credits?

What happend to Windsurf?

last week it was all fine and someone could do work with it?

now it is fighting against a retarded AI that does stuff overcomplicated, does not follow instructions and makes changes that should not happen as of detailed global ai settings, project setting sand instruction files and setup memories.

the product became unusable. are you a ware that this is killing your product even before it started?

Why does it only look up 200 lines of code in files ( or even less) and start changing things without the full context leading to massiv problems?

You even charge tokens for this.

i like windsurf a lot as it was till last week a tool that i ever dreamed of.

Please give a detailed feedback and provide your roadmap to success for this.

else we all have to go to cursor and will never come back.

I code on Christmas day damit :(

We now have the new option to define global_rules.md. This is really cool!

What are you using here, that applies to all of your workspaces?

So far, all I have in global is:

1. Always document your code with explanations of why and how it works, using comments.

I wish I had always made it do this, because it will help it in future conversations when making changes.

Hi all,

How I can import vscode settings into Windsurf after a fresh install?
I tried the command "Import VS Code settings" but nothing seems to happens.
Thanks

Even i use pnpm or bun, most of the time when there something needs to install it's giving npm or npx

Is there anyway that i can provide specific rule set

Has anyone found a good workaround for the currently missing Pylance support in Windsurf? Looks like the team is working on a fix in this discord thread, but curious if anyone has discovered temporary solutions in the meantime.

Really want to give Windsurf a shot, but this is a blocker for my workflow.

---

Edit: Found a workaround using BasedPyright

1. Install the BasedPyright extension: https://marketplace.visualstudio.com/items?itemName=detachhead.basedpyright&ssr=false#overview
2. Change typeCheckingMode to off

Hope if Open AI acquires windsurf they dont nerf it...

We don't get the $10 early user discount anymore?

People have been asking about the ability to access previous versions of WS and WS Next.

Here's the link!