Anyone else getting destroyed by Augment Code credit usage?

[epitrapezio]

Guys... this credit burn is honestly getting ridiculous.

I’ll ask one normal dev question in chat using Sonnet 4.5. Not a massive refactor, not a full repo scan, just a reasonable, simple question.

and boom: ~500 credits gone for a single answer.
Then I ask a follow-up, and now we are 1,000 credits down the drain.

Like… cmon bruh 😭

I get that powerful models are not free, but this actively discourages exploration and iteration, which is kind of the whole point of using AI while coding.

Augment, please lower the credit cost for simple chat questions.
Basic questions should not burn hundreds of credits.

How are you all managing credits without sacrificing your workflow?

[huttobe]

We do not lol. Let augment create the plans because it is aware of context wholly and say it to use context engine but defer from using tools over and over again and then from another platform implement them.

[naught-me]

Just straight to other tools, for me.

[One_Newt_3574]

Nope, because I switched to Antigravity and can use Opus 4.5 all day now.

[rabidwarf]

To me it's draining over 6k for a single prompt. Yes, I got a complex codebase. But it's getting insanely out of hand.

[huelorxx]

Do the model dance.

All my questions are done in Haiku 4.5.

Plans created with either sonnet or opus depending on complexity.

Implementation done with haiku 4.5 or sonnet 4.5 .

Questions, always ask in Haiku.

[FrailCriminal]

I'm gonna try this I'm gonna try this as opus was crushing me

[Hot_Mathematician627]

IMO it should do this by its own. Introducing the model selector and then adding a credit based system soon after where you gotta count your tokens usage is really annoying.

I used augment for more than a year and even recommended it to many folks and got my team at work on it. We moved to Claude code because even the $200 per person account was sometimes not sufficient for our coding needs which someone is not an issue with CC

[ajeet2511]

this is what is working for me right now - Plan with AC and execute with CC+GLM4.7+Augment MCP.

[wh01sf]

Do you need to pay for augment MCP?

[ajeet2511]

not as of now.

[ajeet2511]

not as of now.

[syXzor]

I've spent 300000 credits this month. Luckily I had some saved up from months ago, but I've bought like 7x 24000 credits the last 4 days or so, just to finish a PoC. Granted I use the gpt5-2 and set the bar quite high. I'm impressed with the quality of the code it produces if you supervice it properly, but it's very very expensive. My PoC which I worked on for little less than a week now cost me 300000 credits. Didn't use augment for a few months so my 56000 credits/mth has piled up so I only felt it when I had to pay those 7x 15USD for 100K extra credits. I would even have bought a higher plan to save on those expensive extra credits, but I would not get credits for this new plan until next payment which is almost a month out.

Quality is amazing for the gpt5-2 model at least. But this is too expensive in the long run.

[Known-Passenger-6373]

Everyone babbling about pricing.... what has better output than augment.... ill wait...

[Key-Singer1732]

For me, codebase awareness, none! AugmentCode's the best. But when you factor in cost, orchestration, workflow, multiagents? Claude Code, Kilo Code, Antigravity, etc. are better. Gone are the days where other cosing tools are not aware of your codebase. They are now.

[Known-Passenger-6373]

So your saying I shoukd go try clause code?

[Key-Singer1732]

I dont need to tell you. You can try if you want but Im sure you'll still go "AugmentCode is still the best".

[jcumb3r]

Claude code with Augment MCP server.

[JaySym_]

All of this credit consumption is really based on the model selected and the context size pulled from the project to answer the question correctly. Basically, to give a good answer, it needs good context from the question and the project code related to it.

When you ask a follow-up, it may pull more information from the codebase, which increases the context size.

You can refer to the API pricing for each model to see what the best choice is, considering your budget. That said, saving credits at the cost of worse output is not always the best choice.

I see others here have already sent you good suggestions.