Feature Requests

Let's say i have 500 credits this month that I purchased. I bought them with my subscription. But I couldn't program much this month so I only used 100. Well now the next month you charge me another $15 and delete the 400 credits I didn't use? Come on now. Now if I hit 501 credits this month I'll have to purchase more. When you just stole 400 credits from me. Product is amazing by the way. But you guys have to get the payment structure ironed out. I want you guys to make money because I think the product is great. But you guys need to fix this so people like myself don't want to even think about leaving. Because the competitors will copy/steal whatever innovations you guys come up with eventually. You need to be innovative and honest about your payment structure. At least allow 50% of credits to be rolled over. That way when I see $15 come out of my bank account, I don't think "dang.. they just stole 200 credits from me." Instead I'll think "Yes! Now I have even more credits for when I want to spend a week straight coding!"

I have been losing a significant number of credits due to "Cascade error" and messages indicating "This may be stuck. Please Try cancelling." I would like to request the implementation of a feature that automatically refunds credits for requests that result in these errors.

Windsurf already offers powerful personalization through: Global and workspace-specific rules (e.g. .windsurfrules or global_ rules.md ) to guide Cascade’s style, reasoning, and output Workflows stored in .windsurf/workflows/ as repeatable, step-by-step task sequences Skills that extend Cascade’s capabilities with custom tools/behaviors Memories and other context files However, these are currently managed locally (per-user or per-workspace), which creates friction for teams. Developers often recreate similar rules, workflows, and skills across projects, leading to inconsistency, duplicated effort, and “drift” in team standards. Proposed feature: A centralized, shared library for teams Introduce a team-level shared library (or “organization knowledge hub”) that allows: Central storage & versioning — A cloud-backed or git-synced repository of approved/shared rules, workflows, skills, and memories that can be maintained by team leads, tech leads, or a dedicated “AI standards” owner. Easy discovery & subscription — Team members can browse/search the library inside Windsurf (e.g. via a new “Team Library” pane in settings or Cascade sidebar) and one-click “subscribe” to pull the latest versions into their workspace or global scope. Granular attachment — Apply shared items selectively: Globally for the user To a specific workspace/repo To certain file types/folders (via globs, similar to existing rule scoping) Version control & updates — See when a shared rule/workflow/skill was updated, review changes, and choose to pin a version or auto-update. Optional approval flow for critical teams. Overrides & composition — Allow local/workspace overrides that extend (rather than fully replace) shared items, so teams can customize without breaking consistency. Searchable & documented — Each shared item should support rich markdown descriptions, example usage, and tags (e.g. “security”, “frontend”, “testing”, “prisma”).

As a Team Plan admin, I need the ability to purchase and assign add-on credits to individual team members rather than being forced to purchase credits that are pooled and shared across the entire team. Current Behavior: Each team member receives 500 base prompt credits per month (individual, per seat — this is fine). When base credits are exhausted for one or more members, the only option to top up is to purchase add-on credit packs (e.g., $40 for 1,000 credits). These add-on credits are pooled across the entire team, meaning all members draw from the same add-on balance — there is no way to allocate extra credits to a specific individual. Expected / Requested Behavior: Team admins should be able to purchase add-on credits for a specific team member rather than only for the whole team pool. Alternatively, provide an option to set per-user add-on credit limits or allocations so that admins can control which members can access how many additional credits. Use Case / Business Justification: In a team of 10+ developers, usage patterns vary significantly: Some members (e.g., those working on high-complexity features or AI-heavy tasks) exhaust their 500 credits quickly. Others may barely use half their allocation. Purchasing a shared pool to cover heavy users means all members can draw from it, which makes credit usage unpredictable and hard to manage from a budget perspective. There is no fair or granular way to top up only the users who need it. Individual add-on credits would allow: Budget control per team member or per role. Predictable credit consumption tracking. Fairer allocation — no risk of one member consuming credits intended for another.

When will you be able to BYOK for Gemini, thanks

Add solution to enable persistent memory across sessions per project so the agents can build up inherent memory within a project and user can ask agent to refer to this memory as needed This could be enabled via enabling plugins support and the we can use things like https://github.com/thedotmack/claude-mem

SWE-1.5 not able to use chrome-devtools mcp or any browser to test its work The agent reports: unable to use the Chrome DevTools MCP at the moment due to connection issues. All the MCP calls are failing with "transport error: failed to write request: the pipe is being closed."

Deep wiki is great but many times the whole line of code is confusing not just a single function it would be great to have the ability to mark the whole line and then use deepwiki on that:)

I am trying to buy credits, until 10 days ago it was normal but now a confirmation window from the financial institution appears when opening and authorizing the purchase of the refused purchase. I tried with 3 different cards and 3 different institutions same error I tried with Google Pay and link same error cards are working because I made purchases on Mercado Livre without problem and when contacting the banking institution the answer was that the store sent the wrong CVV for confirmation. I checked the CVV is correct the error is in the Wind Surf confirmation method