Windsurf burns through credits by continuously correcting itself

In this state this hardly more than a fun gimmick. I've tried four different project types now (composing a bash script, setting op a small Spring Boot project, setting up a React/Zustand based web UI and some CUDA code) and in all cases it just loses track once you get beyond even the smallest of setups. As I type this it's in a 20 step flow of fixing a bash script, run it, see a problem, claim it fixed it, run it, same problem, tries variant it already tried. Whatever the combination of memory, attention and model is causing this behavior is unclear to me. I've upgraded a few hours ago and I've burnt through 15% of my total monthly budget. And that's ignoring the fact that it bails on generating edits about 30% of the time with an error (I suspect due to the large size of the scripts it created and them being too large an amount of input tokens for an edit or just service outages, hard to say). Is anyone actually using this for production level codebases? Also, any model other than Claud is doing this thing where it suggests a fix without actually editing the files until you tell it something like "do it".

P.S. It would be an interesting optimization to have some sort of (non LLM/ML based) short term history of generated content so it can avoid burning credits on generating the same command line invocations over and over again. As per the above mine is continuously doing a fix and then "Let me run our updated script that now properly handles project IDs and follows our standardized service account structure:" which has been the same bash command for about an hour now.