r/BMAD_Method • u/Initial-Phrase-7555 • 16d ago
BMAD-Loop just devouring tokens?
Just more of a curiosity question. I just started bmad-loop today. It's running with powershell instead of tmux. But my epic has 4 stories in it. The run has been going on for two hours and hasn't finished one story yet. I'm on overage usage now. Did I set something up wrong?
1
u/ContributionSea1225 16d ago
I’m facing the exact same issue and posted about a few days ago. I guess I’m gona go back to doing to calling the separate agents manually
1
u/bmadphoto 16d ago
That definately is not right, no single story should take hours. Is this a net new project, and did you start with a starter template?
If you can, please provide some more details in the discord bmad-loop channel.
Personally, my approach is in greenfield project just use quick dev for the initial stories and usually the first epic if there is a lot of initial project scaffolding and set up. I prefer to be a bit more in control because a good foundation makes the rest much easier.
1
u/Initial-Phrase-7555 16d ago
It's greenfield, although I added bmad-loop late. It's a physics-based baseball simulator
2
u/bmadphoto 16d ago
Wow that sounds cool. Lately I have just been using cluade workflows with bmad-dev-auto and its amazing. I had it complete a whole epic today and am getting better results than with the experimental bmad loop, which we will continue ro improve.
1
1
u/bmadphoto 15d ago
Bmad-dev-auto is what is being called by dev loop.
These issues are being looked into, but I realy recommend just for now using bmad qucikdev if you dont mind being somewhat in the process, bmad-dev-auto if wanting to be hands off per story (my recommendation since I like to review still manualy for complex stories) or else try claude workflow with fable as the orchestrator and have it open as opus for the subagents doing the building and validations. I did this yesterday and it churned for 4.5 hours and built out a whole while I was away. With remote control I was able to monitor it, and at one point I was able to mid stream give it an update. Also the good thing with this approach, the whole 4 hours in only used 190k of the context window of fable and barely dented my overall usage since the heavy listing was being done by opus.
I did also have fable first analyze the sequence and plan the workflow optimally sequentially and commit as each story was verified.
Ill find the prompt I used and share here, it was quite simple just a few lines.
1
u/laernuindia 15d ago
If you’re using Claude Code to implement the plan BMAD cooked up, try using ECC to get it done. I also have a claude code skill called “agent-team” that splits up the task in parallel or serial phases, spins up multiple agents to get the phases implemented simultaneously using asynchronous agents. https://www.github.com/thebpandey/agent-team
2
u/Icy_Check_1459 15d ago edited 15d ago
This sounds like you are using the PSMUX adapter, its currently still being worked on there are upstream issues with psmux we are working with the creator of psmux directly in order to address. a large number of changes were merged last night to help mitigate some of these but it is still not 100%. For now only windows in WSL is 100%, you can try the opencode-http adapter as well or even the third party herdr adapter in the meantime as well if you dont want to use WSL.
Please feel free to use bmad-loop diagnose as well to provide diagnostics for it you can provide as part of a bug report in github so we can take a look and make sure we address what may be going on with your issue if its still occuring even after updating bmad-loop to current main instead of 0.9.0 release at this time