Amp chewing through balance excessively

Amp
1

Hi folks — first off, I just want to say how much I love the new tool. It’s a massive improvement over the previous version. That said, I’ve noticed it consumes the subscribed balance quite quickly. In many cases, just a few prompts can use up an entire purchased package.

From what I can tell, this seems to be driven not only by the amount of code being generated and modified, but also by the multiple test builds it runs — which, to be fair, is a very cool feature — along with the self-checking harness that catches and corrects syntax issues it may introduce.

Still, the net effect is a noticeable spike in usage that depletes balances faster than expected. Is there any way to reduce this — perhaps through a setting that limits test runs — or alternatively, to adjust the pricing tiers so the cost isn’t quite as hard to justify?

1 Like
2

Hey @ericwelsh.dev thank you for reaching out to us.

Indeed, Amp can eat a lot of tokens. This is by design with all the tool calls it makes and to provide excellent end-to-end user workflows. This saves you a lot of time and Amp handles all for you.

You can always prompt Amp not to run tests at the end of an implementation or bug fix and it stops exactly at that checkpoint. Or you can press the ESC key (IDE) or CTRL + C (CLI) to stop the agent at any point.

Additionally, divide your tasks into smaller sub-tasks and start a new thread whenever possible. This helps to prevent context pollution which often leads to hallucinations or loops.

Thank you.

1 Like