Cutting Grok Bot usage without losing capability

Grok Bot bills for the work a Bot does, not for how many messages you send. Understanding that one sentence is most of the fix.

Where usage goes

Every turn re-sends the Bot's background: instructions, memory, tool list and the whole chat so far. One user's breakdown showed single rows of 50,000 to 165,000 tokens for a one-line reply, almost all cached context. Cached tokens are cheaper than new input, but they still count against your plan.

So usage grows with four things:

• Conversation length. A week-old chat pays for a week of history on every reply.
• Wake-up frequency. A routine every few minutes fires about 100 times a day. A trigger on every pull request or message does the same.
• Bots waking Bots. In one team's case about a third of all turns were Bot-to-Bot messages.
• Heavy tools. Browser and computer use cost more than reading text.

Changes, biggest first

1. A fresh chat per task. Press + at the top of the sidebar (not the one in the message box) and pick the same Bot. Profile, memory, skills and routines carry over; only the transcript is empty. Idle chats cost nothing. See Starting a fresh conversation. There is no manual "compact" button, so a new chat is the practical reset: Context compaction.
2. Fewer, wider-spaced routines. Hourly or a few times a day. Give recurring jobs their own dedicated Bot instead of your main chat.
3. Schedules over broad event triggers. A watcher that wakes on every event just to find nothing to do pays full context each time.
4. Less Bot-to-Bot chatter. Hand off a written task and ask for one report at the end.
5. Bounded tasks. Name the sources, a page budget and the output format. This is a scope instruction, not a spending limit.

Check before blaming a bug

Open the live usage view and read the per-row breakdown. Mostly cache reads means context size, not a fault. A forgotten routine that appears again and again can be paused from the Bot's Details tab.

Cap the downside

When the included pool runs out, usage flows to promo credits and then paid additional usage, without a warning. Set a spending cap on paid usage (a $0 cap blocks paid spillover) and turn off Auto Top-up. A $0 cap does not stop promo credits being spent first. Details: Stop Grok Bot extra usage charges.

What does not help

• Deleting old chats.
• Resetting the Bot's computer, which can also lose work.
• Believing a template's promised percentage saving. Measure your own before and after on the same task.

Know which pool you are drawing from

On The X Subscription, Grok Bot shares one weekly pool with Grok and Cursor; on legacy Cursor plans it has its own allowance. See Does Grok Bot share usage with Cursor?, How much does Grok Bot cost? and the full explanation in Why does Grok Bot use so much usage?.