Cursor Team: Grok Bot is using my first-party / Cursor Models allowance

Support Help
1

I’m on Cursor Teams.

Grok Bot usage is showing up under the first-party (Cursor Models) allowance on my seat(Cursor Team), and it is increasing that percentage.

On Pro, staff said Grok Bot has its own weekly pool and should not consume Cursor IDE usage.

Is this expected on Teams? Does Grok Bot share the seat’s first-party quota?

Thanks.

7

Hey @harrisonhou
Grok Bot doesn’t use your Cursor Models allowance on Teams (same as on Pro). It has its own separate weekly pool, which you can see in the Grok Bot app.

The dashboard just lists the grok-bot-* rows under Cursor Models because it groups by the model that served the request, not by product. So it looks like it’s counting against your quota, but it isn’t, and the Cursor Models % at the top only reflects your own Cursor usage. This is a display issue we’re tracking.

Let me know if anything still looks off!

8

Thanks for the clarification.

We still have some concerns. On the dashboard, grok-bot-default is currently occupying a share of the usage percentage. From your explanation, that traffic should not count against our Cursor Models allowance — so the percentage we’re seeing looks wrong.

Our worry is that if Grok Bot usage continues to be included in that number, the displayed usage could exceed 100% (or look like we’ve exhausted Cursor Models) even when our actual Cursor usage has not. Could you please confirm:

1. The grok-bot-default percentage currently shown is only a display/grouping issue, and it does not consume our Cursor Models allowance?
2. We will not be rate-limited or blocked on Cursor Models because Grok Bot traffic inflates that number — even if the dashboard shows ≥100%?
3. Is there an ETA for separating Grok Bot usage from Cursor Models on the dashboard, so the percentage at the top matches real Cursor usage only?

Happy to share a screenshot if that helps.

9

Hey @harrisonhou,

  1. Display-only. The grok-bot-* rows sit under Cursor Models because the breakdown groups by model, not by product - they aren’t drawn from your Cursor Models allowance.
  2. No rate-limiting from it. Grok Bot has its own separate weekly pool (shown in the Grok Bot app), and the Cursor Models % that governs your limits only counts your actual Cursor usage, so an inflated-looking row won’t push you into a limit.
  3. Separating it out in that view is on our list - no timeline to share, but I’ll post here when there’s an update.

One heads-up: cloud agents launched from Grok Bot do count toward your Cursor plan.

10

That does not look like it. It seems like it is taking from the first party quota.

image
image1059×272 9.04 KB