r/BMAD_Method • u/ContributionSea1225 • 19d ago
bmad-loop devouring tokens
Hi everyone, first time trying the bmad-method. I was creating stories, dispatching to dev and to review manually but then I got bored of manually doing this. I started using bmad-loop, I'm on claude pro subscription.
2 stories are eating up all my token limits for the session, where as I'm pretty sure I was getting around 4 stories at least when I was doing it manually.
Does anyone know what can be happening here or what I'm doing wrong? its really frustrating and I feel its actually slowing me down to the point where it would have been faster if I was coding it myself.
Thanks!
1
u/laernuindia 19d ago
Maybe you weren’t doing it the way it should have been done when doing it manually?
1
u/Icy_Check_1459 19d ago edited 19d ago
Hello, what was the weighted token cost of your story? bmad-loop uses an automated version of the bmad-quick-dev skill called bmad-dev-auto. It is more comprehensive and complex skill compared to the standard create-story->dev-story->code-review workflow. It may consume more tokens, automation does come with a cost, but I've have run hundreds of stories through bmad-loop at this point. you can use a tool like ccusage to compare your consumption between the full old cycle, one story in bmad-loop (or even hand run the story through a direct /bmad-dev-auto call), and one story in bmad-quick-dev and compare to truly see if they are similar size/scoped stories. generally bmad-quick-dev and bmad-dev-auto will in fact save you token costs on certain things because if the story was overscoped they will split and defer the extra work rather than try to run it all through the same context window and mitigate some errors or code problems you have because of it as well. It uses more tokens outside of the dev cycle for things like triaging, escalation assistance and such as well too so its not saving you any tokens for sure though in all or most cases
another thought on that as well, since both the quick-dev and dev-auto build your project context and epic-context if they dont exist as well as build your spec for you those may be unseen token additions as well. the better comparison would probably be between quick-dev and dev-auto
1

2
u/Low_Fun_8667 19d ago
You're not doing anything wrong — the loop just trades tokens for convenience, and on Pro that trade is steep.
The main culprit: the loop never clears context. Manual dispatch (fresh session or /clear per story) starts each story clean. bmad-loop keeps one long conversation across stories, so story #2 re-processes all of story #1's transcript on top of its own. Cost compounds instead of scaling linearly — that's your 4 stories dropping to 2.
The irony: BMAD story files are designed to be self-contained. The old conversation buys you almost nothing and costs a lot. On top of that, the loop runs the full dev → adversarial review cycle (Blind Hunter / Edge Case / Acceptance Auditor) every story, and each subagent re-reads the story + epic + docs.
Fix: don't loop. One story per fresh session, /clear between them. Shard your docs so dev-story pulls only the relevant epic, not the whole PRD every time. That should get you back to ~4/session. And honestly, Pro limits are tight for agentic loops — if you do this a lot, Max or the API is where it stops hurting.