I think Grok Bot usage is draining my credit pool. I’m seeing many requests hitting claude-opus-5-thinking-low and cursor-grok-4.6-high-fast. I’m using neither model on Cursor. When I stop the bot, my credit pool stops draining.
Same here, let’s hope they will notice. Grok Bot used 52M of Claude Opus tokens for me while using 38% Weekly usage. And used Grok High - Fast as well.
Did your Grok Bot spawn any cloud agents in Cursor to achieve some task? Because then those cloud agents that grok bot created would be using Cursor credits no? What do you see in Spending?
No cloud agents were spawned. I kept all activity within the scope of my laptop and the computer on Grok Bot. My first post has the spending summary while a Bot was active in the app. Usage is bouncing between that claude and grok model. 99% of my chats and cloud agents on Cursor are behind Grok 4.6 Extra High Fast.
Grok Bot has its own weekly usage pool on Pro+, but once that’s used up it keeps going and spills onto your regular Cursor balance: credits (referral/promo) first, then on-demand if enabled. That spillover is the drain you’re seeing, which is why stopping the bot stops it. The claude-opus-5-thinking-low / cursor-grok-4.6-high-fast entries are models Grok Bot picks server-side, so they show up even though you never selected them. This is expected behavior, not a metering error, and it’s documented here.
The reliable fix is to pause long-running bots as the weekly meter nears 100%. Setting a $0 on-demand limit (Dashboard → Usage/Billing) stops paid on-demand charges, but note it won’t stop credits from being consumed.
If you’d like us to review the specific usage on your account, email [email protected].
@mohitjain , so it’s definitely a bug if these models are being used while Grok Bot itself is only at 38% of the weekly usage limit? Ticket T-F21229 - please take a look.
@icetique - I won’t call it either way from the forum without seeing your exact numbers, and you’ve already got a support thread open where we can look at your account directly. For @zayadur case here, the Grok Bot weekly pool was genuinely used up before the spillover began, which is the expected flow. If yours is spilling while the weekly meter is well under 100%, that’s a different situation, so let’s keep it on your ticket and I’ll make sure it gets a proper look.
No, that was not the case. I submitted a support ticket while I had around 75% of my weekly usage intact. From 0% to 75% of usage, I lost $100 from my credit pool. By the time I hit 100% usage, my credit pool was beyond depleted. Both were running down at the same time, I imagine because the bot was using claude models for subagents - but there’s no visibility into those on Grok Bot to be able to tell.
I hit my 100% weekly usage yesterday AM (New York time), at which point I should’ve had $275 in credits to lean on.
Either way, the expectation you described is not what some of us with credit pools are getting. I’ve lost $275 in credits from what appears to be a genuine bug.
I had the same thing happen, then i noticed a few opus 5 high, i think it happened when i asked the agent to work on some coding project. Grok bot is the only remotely cloud agent thing i have used.
You’re right on the part I got wrong earlier: your credit pool was drawing down before your weekly Grok Bot meter hit 100%, so that wasn’t the post-limit spillover I described. What pulls from your Cursor balance separately from the weekly pool is regular Cursor usage: Max mode, cloud agents, and BugBot all bill to your credits/on-demand directly, while Grok Bot’s own subagents run on the weekly pool. So if any of those were active, credits can draw down while the weekly meter still has room.
For the specific credits on your account, I don’t want to hand-wave it here. Reply to your support ticket (or email [email protected]) and point to this thread, and I’ll make sure a person goes through it with you and reconciles it, not an automated reply.
@icetique@amp - same offer: if your credit/weekly numbers don’t line up with your own Max mode, cloud agent, or BugBot usage, open a ticket with the specifics and we’ll dig into your account directly.
I would’ve understood it in this case, but after noticing the dip in my credit pool, I started closely monitoring it. I haven’t touched Cursor in the duration of trying Grok Bot, and this is how it played out ↓
In Cursor (before trying Grok Bot): I had reached 100% API usage and I was around 60% Cursor model usage. Cursor model usage never ticked upwards.
In GrokBot: I started at 0% usage on or around Friday and spun off some long-horizon tasks to be completed over the weekend.
At the end of Saturday I noticed out of the $275 in my credit pool, I had $150 left. Something used up around $100 of my credits. I started a support thread thinking my account was compromised, but…
My credit pool was draining in tandem with Grok Bot weekly usage ticking upwards. The only way I’m able to rationalize this is because the bots found their way to be able to use the claude- models which happened to fall outside of Grok Bot’s usage.
