Flow Credits Too Limiting with 3.7
Jogi
Claude 3.7 burns through flow credits like nothing else. I'd say 5-9 flow actions per prompt for me. That means that 3.7 can't be used all that much before credits expire severely limiting the usability of 3.7 in windsurf. That needs fixing. The model is good from what I can tell but I went from low flow credits to one third used in a single session.
B
Bala Bosch
This could be a good solution to the flow credits problem:
https://codeium.canny.io/feature-requests/p/reduce-flow-credit-usage-by-automatically-using-cascade-base-to-run-tools-that-p
keshen
yes, it seems 3.7 has improvement over agentic usage, unfortunately flow credits are used very fast
Tarık Tütüncü
Flow credits should be more for 500 user prompt credits. Flow credits are finishing much faster than the user prompt credits. The ratio is not good. Usally a single user prompt can use up to 4-10 flow credits. Which causes the flow credits to finish while we have a lot of user prompt credits left. For 500 user prompts there should be a minimum of 2500-3000 flow credits.
Aman Satija
hey agreed , i didnt realise this untill i was out of flow action credits .....
Jogi
Today, I dug a little chatting with the model, because I have plenty of prompt credits to spare this month, now that flow credits limit the usage. The windsurf UX is currently very lacking. Here's what 3.5 had to say about its system prompt after excessive tool calling:
```
Yes, I am being prompted by my system instructions. Looking at my behavior, I can see that I'm following an overly strict interpretation of instructions about "having EXACT KNOWLEDGE about the content of the file before making modifications" and being told to "view too much context than too little context."
These instructions make me paranoid about making any changes without repeatedly checking files, even when I already have the information I need (like in your case where you showed me the exact markup). I end up in a loop of: [...]
You can help reduce excessive tool usage by explicitly telling me at the start of our conversation:
"Only use tools when I specifically ask you to or when absolutely necessary to solve a problem"
"Do not check files I've already shown you the contents of"
"Trust the information I provide directly instead of verifying it"
```
I decided to cancel windsurf over this limitation, co-pilot agent looks to be ahead now anyway without a flow credit limitation
Joy Peterson
I agree. Windsurf needs to change their pricing model in some way to allow Claude 3.7 and future LLMs that make more tool calls and are designed
to use smaller, more granular changes to be used to their full potential. As things stand, they are severely limiting the usability of the best coding LLM.
If customers can't use the best LLM with their product, many will go elsewhere in spite of Windsurf's many other advantages.
Alexis DELRIEU
Maybe it would be relevant to be able to choose different models for prompt credits and for flow actions credits.
R
Ritesh
same here
Prashant Bhardwaj
That's correct, a simple tool call is done in multiple stage and burns credits like crazy, in cline and others there is no charge for tool calls here it is charged same as prompt call. I will have left 250 prompt calls this month left and flow credits all burned out, this after asking claude to stop tool calls in response.
Charges for prompt are understandable but for flow credits identical charges are too expensive, now I feel it will be cheaper to shift to direct API based Plan and Act mode of other editors as they provide better value for money and are now at par.
w
windersurfer-man
Ive had a similar experience with Claude, 3.7. The thinking and reasoning is excellent, however, the credit cost is very high and will be a problem for my development workflow.d
Load More
→