Pace Grok Bot weekly allowance on Ultra (and Heavy)

Ultra and linked SuperGrok Heavy share the highest Grok Bot weekly pool. That pool can still hit 99% in a few days when long chats, dense routines, and tool-heavy turns stack. Official metering: Plans and billing. Staff playbook: forum 171221 (mohitjain, Sep 10, 2026).

What the meter counts

Grok Bot bills work the bot does — tools, browser use, subagents, and re-reading the conversation each turn — not message count. On that Ultra report, support saw most of a multi-day burn as cache reads from a long-running conversation (~84% of a large token export). Each new turn re-reads history, so a fat thread gets more expensive every reply.

Check the plan / Usage screen before a big job. You can ask the Bot to audit its own recent usage when the percentage climbs fast.

Biggest wins (staff order)

1. Fresh conversation per task. Use Reset chat on the same Bot so Identity (name, memory, routines, skills, connectors, computer files) stays and the transcript clears. A long session costs more per turn than a fresh one doing the same work. Steps: Reset a Grok Bot chat without cloning the Bot.
2. Space routines. A routine every few minutes is on the order of ~100 fires/day. Prefer hourly or a few times a day. Put recurring jobs on a dedicated Bot, not your main chat thread.
3. Delegate heavy implementation to Cursor cloud agents. Bot coordination stays light; model work for the agent run draws the separate Cursor plan allowance. Cloud agents are the documented exception that touch Cursor Models usage — see Why Grok Bot rows show under Cursor Models usage.
4. Scope tightly. Prefer short, single-outcome tasks over open-ended “keep watching / keep coordinating” sessions.

Related burn paths

• Multi-Bot review loops: Stop multi-Bot review loops from burning weekly usage.
• After the week hits 100%: Control Grok Bot On-Demand after weekly usage.
• Ultra vs Heavy for Bot quota alone: SuperGrok Heavy vs Cursor Ultra for Grok Bot.

Pitfalls

• Linking Heavy on top of Ultra (or the reverse) does not enlarge the Bot weekly pool — quotas do not stack.
• Reset chat clears the transcript. Export anything you must keep first.
• On-Demand after 100% is optional spend on the Cursor account; turn the limit to $0 if you want a hard stop.