Why does Grok Bot use up my weekly usage so fast?

What you are actually paying for

Staff on the official community forum have explained the model the same way in several threads: Grok Bot bills for the work the Bot does — tool calls, browser use, sub-agents and re-reading the conversation on every turn — not for how many messages you send.

That last part is the one that surprises people. Each call re-sends the Bot's background: its instructions, memory, tool list and recent chat. One user's breakdown showed single rows of 50,000 to 165,000 tokens for a one-line reply, almost all of it cached context. Cached tokens are billed at a much lower rate than new input, but they still count against your plan.

So usage grows with:

• Conversation length. A Bot that has been in one chat all week pays for that week of history on every reply.
• How often the Bot wakes up. A routine every few minutes fires around 100 times a day. Event triggers that fire on every pull request or message do the same.
• Bots waking Bots. In one team's case, about a third of all turns were Bots messaging other Bots.
• Heavy tools. Browser and computer use cost more than reading text.

The changes that help most

In the order forum staff recommend them:

1. Start a fresh chat for each task. Press + at the top of the sidebar and pick the same Bot. The Bot keeps its profile, memory, skills and routines; only the transcript starts empty. An old chat left idle costs nothing. See How do I start a fresh conversation with the same Bot?
2. Space out routines. Prefer hourly or a few times a day. Put recurring jobs on their own dedicated Bot, not in your main chat.
3. Use schedules instead of broad event triggers. If a watcher wakes on every event just to decide there is nothing to do, it is paying the full context cost each time.
4. Cut Bot-to-Bot chatter. Hand off with a written task and ask for one report when done, instead of status pings.
5. Keep tasks bounded. Name the sources, a page budget and the output format. This is a scope instruction, not a hard spending limit, but it reduces work.

Check before you assume something is broken

Open your live usage view and look at the per-row breakdown. If most tokens are cache reads, the cause is context size, not a bug. If a routine you forgot about shows up repeatedly, pause it in the Bot's Details tab.

On the newer X Subscription plans, Grok Bot draws from the same weekly pool as Grok and Cursor; on older Cursor plans it had its own weekly allowance. See Does Grok Bot share usage with Cursor?

What does not help

• Deleting old conversations does not reduce usage; idle chats cost nothing.
• Resetting your Bot's computer does not reduce usage and can lose recent work.
• No template, including ours, can promise a fixed percentage saving. Measure your own before-and-after on the same task.