What to do when Grok Bot usage does not match

First, make sure it is a real mismatch

Open the account menu in each view and confirm the email address. A personal Cursor account, a Teams seat and a separately linked Grok account can create confusion if you compare the wrong sessions.

Then reopen Cursor Settings, select Usage & Billing and refresh the page once. Cursor's official settings guide identifies this page as the place to see weekly included and on-demand usage.

Record the evidence before changing anything

Write down:

• the date, time and time zone;
• the Cursor account email, with the middle characters redacted;
• the weekly included value shown in each view;
• the on-demand value shown in each view;
• the Bot task or routine that most recently ran;
• the task start and finish times;
• screenshots of both views.

Do not post screenshots that reveal billing details, email addresses or company data in a public forum.

Use the account page for the account totals

Use Usage & Billing when deciding whether the account has included usage left or has started using on-demand billing. Keep the other reading in the support record, but do not invent a per-task cost or assume one view is delayed unless Cursor confirms it.

Stop adding variables

If the difference appeared after a new routine started, pause that routine and do not schedule another one. Keep existing business workflows under human review while you establish whether usage continues to change.

You can still inspect completed work and routine history. Do not delete the routine or its run records before support has the evidence.

Escalate with a useful report

Contact Cursor support if the views still differ after confirming the account and refreshing the current session. Send the timestamps, both readings, the relevant task or routine and the redacted screenshots. Ask which value applies to the account and whether the usage can be tied to the recorded run.

After the issue is understood, use a daily usage-monitoring routine or manual log during the next week of testing.

Sources: Grok Bot settings and Grok Bot plans and usage.