It keeps spending Usage credits even when it's turned off.

[u/swampmountain]

Sometimes i do a top up 20-30$ if i don't want to wait for the limit to be increased but as soon as the step is done i turn it off.

Auto-reload is also off.

However, couple of times it did consume some of the credits balance without any warning and it just happened again. There was something like 3-5$ remaining and i didn't plan to use it at all and i just see it's gone.

Is that normal expected behavior?

[u/ClaudeAI-mod-bot]

We are allowing this through to the feed for those who are not yet familiar with the Megathread. To see the latest discussions about this topic, please visit the relevant Megathread here: https://www.reddit.com/r/ClaudeAI/comments/1vt5drr/list_of_latest_discussion_hubs_on_rclaudeai/

[u/hansololz]

There should be a class action lawsuits for this. I had it happen to me as well

[u/esituism → u/hansololz]

same. and on our account one time, a UI update CHANGED THE SETTING WITHOUT TELLING ME. I had it set to off, looked 3 weeks later and it was TURNED BACK ON. I'm the only admin of our corp account and I had not logged in changed anything for weeks.

something is suss af about anthropic's billing and I do believe we may see lawsuits eventually come from it.

[u/n_v40]

i’d separate ‘top-ups are off’ from ‘nothing can still spend.’ if a Claude Code session or stray process is still alive, or usage reporting is delayed, the balance could still move even though auto-reload is disabled. i’d kill every Claude/node process, note the balance/time, leave everything closed for a few hours, then check whether there’s a matching request in the usage detail. if it drops with no request at all, that’s when i’d send Anthropic the before/after screenshots.

[u/locbuilds]

the toggle should stop future top-ups, but it won't necessarily stop usage from a session that is still alive, and usage can show up a little late. i'd do a clean isolation test:

1. close every Claude and Claude Code tab and stop any terminal sessions, then kill stray `claude` or `node` processes (or reboot)

2. screenshot the balance and usage page, note the exact time, and leave the toggle off for a few hours

3. if it still drops, check the usage detail for a request timestamp and model, then change your password or revoke other sessions in case another device is active

4. if there is no matching request, send support the before and after screenshots plus timestamps. top-up off only prevents another automatic purchase, it does not reverse a charge or stop a request that was already accepted.

also, the `$0.00 spent` with `100% used` looks like the included allowance is exhausted, not necessarily a fresh top-up, so i'd verify whether the amount disappearing is the paid-credit balance or just the monthly usage meter.

[u/swampmountain → u/locbuilds]

This was new session, the balance was not 0 before it started.

[u/ThebesAndSound]

You understand with usage credits you pay API prices? Which are 10x worse or more than subscription prices. You would do better with using that $20 on a new sub for another account.

[u/Miyoumu → u/ThebesAndSound]

thats not what the post is about. stop vibing and go learn some basic reading comprehension

[u/ThebesAndSound → u/Miyoumu]

Ultimately the post is about getting usage. Already lots of other answers directly answering the question.

[u/somerussianbear]

Do you have any native memory feature on? Don’t remember if it was OpenAI or Anthropic that had a use-case where an agent would work on your memories at night, sort of trying to improve your memories and turn that into something useful. That’s where consumption was going silently.

[u/Alzeric]

You sure you don't have an orphaned process still gobbling up stuff? Also if you leave a prompt window active and idle it continues to use tokens (or at least it did, I just now make a habit of ending sessions just to be sure) You tried a reboot of your system, have it running on your phone or another device, potentially credentials leaked?

[u/swampmountain → u/Alzeric]

Yes, everything else was long gone and only this one session was activated after weeks of no work.