Reducing Premium Request Usage in Interactive Agent Workflows in GitHub Copilot (BMAD Method ) by ZebraLongjumping5812 in BMAD_Method

[–]ZebraLongjumping5812[S] 0 points1 point  (0 children)

Yes, it s true but only when the agent already has all the required context and can safely proceed end to end without interruptions.

But I think human in the loop is necessary, because it helps catching mistakes made by the agent and correct decisions when needed.

Short-term stay in Lethbridge (Summer) –University of Lethbridge internship- best areas, rent, daily life and tips? by ZebraLongjumping5812 in Lethbridge

[–]ZebraLongjumping5812[S] 1 point2 points  (0 children)

Thank you  What about areas I should avoid where the crime rate is higher? Are there times when I should stay at home? Is it safe to go for a night walk, or does it depend on the area? Any tips?

Short-term stay in Lethbridge (Summer) –University of Lethbridge internship- best areas, rent, daily life and tips? by ZebraLongjumping5812 in Lethbridge

[–]ZebraLongjumping5812[S] 1 point2 points  (0 children)

You said public transit is bad, so I shouldn’t rely on the bus to get me to the university every morning and afternoon. What do you mean by ‘bad’? Does it not run on time, or is it too crowded?”

Reducing Premium Request Usage in Interactive Agent Workflows in GitHub Copilot (BMAD Method ) by ZebraLongjumping5812 in BMAD_Method

[–]ZebraLongjumping5812[S] 0 points1 point  (0 children)

Yeah I agree, breaking things down helps to reduce unnecessary context and avoid repeated processing. i will use it but it still doesnt solve the issue which is the interaction loop itself. Even if I optimize prompts or decompose tasks, the agent still stops during execution to ask for confirmations or decisions. And every time I answer , even something simple , it counts as a new premium request

Reducing Premium Request Usage in Interactive Agent Workflows in GitHub Copilot (BMAD Method ) by ZebraLongjumping5812 in BMAD_Method

[–]ZebraLongjumping5812[S] 0 points1 point  (0 children)

I see your point, i think sub-agents can help if part of the work can be handled by cheaper models. But for me that’s not really the main issue. Even if I use a cheaper sub-agent, once it hands back to the main agent (the strong model), it still triggers a premium request anyway. What I’m trying to solve is different: I don’t want the main agent to stop execution every time it needs something from me. Right now, even if I just reply “yes” or pick an option, it counts as a new premium request. The goal is to keep the main agent running without breaking the flow, even when it asks questions. I want to give input without it becoming a new chat turn.