# Grok Bot usage running out fast? How to make it last

Every Bot reply, routine run and Bot-to-Bot message spends weekly usage, and long chats cost more each turn. Find the leak, then make your week last.

*From Learn Grok Bot, an independent guide (not affiliated with SpaceXAI or Cursor). Web version: https://learngrokbot.com/usage-running-out Last verified: 2026-10-06.*

A week of Grok Bot usage goes fast because a Bot is charged for the work it does, and before every reply it reads its whole conversation again. Long chats, frequent routines and Bots that answer each other are where a week goes, and each one has a fix.

**In short**

- Every Bot reply spends usage: an answer to you, each Bot's reply in a group chat, each message between Bots, each routine run.
- A reply costs more in a long chat, because the Bot reads all of it again. Start a fresh chat for each new task.
- Look at your routines next. Pause the ones you don't need and slow the rest to hourly or a few times a day.
- Fewer Bots answering means fewer replies. In a group chat, `@` the one Bot you want.
- If the week still runs out: wait for the reset, set a capped on-demand limit, or move up a tier. A second subscription adds nothing.

## What spends your week

Usage is charged for the work a Bot does to write a reply. The number of messages you send, and how long they are, isn't what's counted.

Diagram: Two things feed the cost of one reply. The first is the whole chat so far, which the Bot reads again every turn. The second is the work it does with its browser, its computer and its helper agents. The reply then comes out of your week.
- The whole chat → One reply: read again, every turn
- Browser, computer, helpers → One reply: the work it does
- Note: each reply comes out of your week

*A reply costs what the Bot had to read and do to write it, however short your message was.*

So the same question costs more in a chat you've used all week than in a new one. On one account, a one-line answer moved the weekly meter by about a hundredth of a percent, and a small web task (open one page, report one number) by about three times that.

Four things count as a reply, and each pays that cost:

- A Bot's answer to you.
- Each Bot's reply in a group chat.
- Each message one Bot sends another.
- Each run of a routine.

## Which habit is draining your week?

Five habits make a week leak. Tick the ones that are yours, and the finder lists your fixes in the order to make them.

**Interactive: Find your leak**

Open it: https://learngrokbot.com/widgets/usage-running-out-leak-finder.html

What it does: Five habits that drain a week of Grok Bot usage: one long chat, a routine that runs too often, a routine on a Bot with a long chat, Bots answering each other, and big jobs handed over without a look at the meter. Tick the ones that are true of you and the matching fixes are listed in the order to make them, each linked to its step on the page.

Its content as text:

### Find your leak

Tick every line that's true of how you use your Bots. Your fixes build underneath, in the order to make them.

All five leaks, in the order to fix them. Take the ones that match how you work.

1. **One long chat**
   Before every reply, a Bot reads its whole conversation again. In a chat you've used all week, even a one-line answer spends usage on the week's history.
   Start a fresh chat for each task
2. **A routine that runs too often**
   Each run spends usage. An hourly schedule, a short interval or a Slack trigger on a busy channel can use up a week in a day.
   Slow your routines down
3. **A routine on a Bot with a long chat**
   A routine's runs happen in its Bot's chat. On a Bot you also talk to all day, every run reads that long chat again.
   Give a recurring routine its own Bot
4. **Bots answering each other**
   Every Bot reply counts, in a group chat and between Bots. A message that wakes a Bot costs a full turn, and its answer can wake the sender again.
   Keep Bots from answering each other
5. **Big jobs, handed over blind**
   Larger and longer jobs use more, and you can't tell how much until one has run.
   Check the meter before a big job

None of these sound like you? Go to If the week still runs out.

Each fix on your list is a step in the next section.

## Make the week last

The five fixes are in order, with the one that usually saves the most first. Only one of them removes anything, and its step says what.

**Walkthrough: Make a week of usage last**

### Step 1: Start a fresh chat for each task

Click **New chat**, the **+** at the top of the sidebar, and type your Bot's name. Pick its row, which is tagged **New chat**, and a second, empty conversation with the same Bot opens.

![The top of the app. The New chat button, a plus, sits beside the search button. In the To field the words Demo Price are typed, and the list under it has two rows: Create Demo Price Bot, and the existing Bot Demo Price Watch, tagged New chat at its right end](https://learngrokbot.com/assets/shots/usage-running-out-new-chat.png)

1. **New chat** is the **+** above this pin, beside the search button.
2. A Bot you already have is tagged **New chat**. Click its row.

- The new chat starts without the old conversation. Open with two lines on what the Bot needs to know for this task.
- Leave the old chat where it is. A chat costs usage only when a new message goes into it, so there's nothing to clear or delete.

> **You should see**
>
> The Bot has a second row in the sidebar, above its main one. The new chat takes its title from your first message.

### Step 2: Slow your routines down

Click the Bot's name at the top of its chat. Its routines are under **Details**, each with its schedule and a switch.

![The details panel of a Bot named Demo Research, on the Details tab. Under Routines are two rows: AI coding assistants weekday digest, marked Paused, with its switch off, and Cursor changelog Tuesday check, Every Tuesday at 3:38 PM, with its switch on](https://learngrokbot.com/assets/shots/usage-running-out-routines-list.png)

1. The schedule. A routine that runs every few minutes is the first to change.
2. A routine whose switch is off reads **Paused**, and a paused routine spends nothing.

- Switch off every routine whose results you don't read.
- Slow the rest to hourly or a few times a day. A routine every 15 minutes runs almost 100 times a day. To change one, click it, choose **Edit**, and finish the message the app starts ("Edit your routine:") with the schedule you want.
- For a routine that starts on Slack messages, ask the Bot to watch one channel and one phrase.

Do the same for each of your Bots.

### Step 3: Give a recurring routine its own Bot

A routine runs in its Bot's chat. On a Bot you talk to all day, every run reads that long chat again, so move the routine to a Bot that does nothing else.

Diagram: The same routine on two Bots. On your main Bot, each run first reads a week-long chat. On a new Bot that only runs the routine, each run reads a short chat.
- Your main Bot's long chat → Each run: reads all of it
- A new Bot's short chat → Each run: reads a little

Create a Bot for the job with **New chat**, then **Create new Bot**, and ask it for the routine in one message: what to do, and when. Then switch the old routine off on the first Bot, under **Details**.

### Step 4: Keep Bots from answering each other

Each Bot that replies in a group chat spends usage, and so does each message one Bot sends another. Keep groups small, and type `@` and a Bot's name to send a request to that Bot alone.

Diagram: You send one message to a group chat. The Bots in it decide who answers, and every answer is a reply out of your week.
- You → A group chat: one message
- A group chat → Your week: each answer counts

No setting stops Bots messaging each other, so tell them. Send each Bot this line.

```prompt
From now on, only message another Bot when it needs to act. No acknowledgments, no thanks, no progress updates. Send one summary when the work is done.
```

A Bot can ignore that line. To be sure a Bot you no longer use can't be woken by the others, right-click it in the sidebar and choose **Delete**. Deleting a Bot removes its profile, its conversation and its routines, so save what you need from it first. Files and sign-ins on the shared computer may stay.

### Step 5: Check the meter before a big job

Larger and longer jobs use more, so find out what a job costs before you hand over all of it. Look at **Weekly usage**, hand over one small piece, and look again.

![The Weekly usage limit card in Settings, Usage and Billing. Under the title it reads Included usage with your subscription. Resets weekly. A bar is barely filled, with Resets in 1 day at its left end and 2 percent at its right](https://learngrokbot.com/assets/shots/usage-running-out-meter.png)

*The card is in **Settings** > **Usage & Billing**. The same percent, as a whole number, is in the account menu, opened from the account button at the bottom left.*

- The meter shows whole percents, so a small piece may not move it. Say where the job ends: "the ten most recent", "one page", "stop and show me before you go further".
- If the first piece moves the percent more than you'd like, split the job, or keep it for after the reset.

If your Bots write code, have them hand the coding to a Cursor Cloud Agent. The agent's work is counted on your Cursor plan, and only the Bot's own turns spend weekly usage.

## If the week still runs out

Some weeks hold more work than the weekly amount covers. There are three ways to keep going, and each costs something different.

| What you do | What it costs | What you get |
|---|---|---|
| Wait for the reset | Nothing | Your Bots stop until the countdown beside **Weekly usage** ends. |
| Turn on on-demand usage with a **Fixed** limit | The extra work, billed through Cursor, up to your cap for the month. A Bot already working can finish past it | Your Bots keep working past 100%. [Set the cap](https://learngrokbot.com/usage-limits#on-demand) before you need it. |
| Move up a tier on the plan you already pay for | The difference in price | More weekly usage. [Pricing](https://learngrokbot.com/pricing#plans) lists every tier. |

A second subscription isn't on the list. A Cursor plan and a SuperGrok or X Premium+ link don't add together: [Grok Bot uses whichever gives more](https://learngrokbot.com/pricing#stacking).

## Check: spot the leak

Try the idea on someone else's setup.

**Spot the problem: One line of this setup will use up the week. Tap it.**

- A research Bot, with a fresh chat for each topic
- A news digest routine, weekdays at 8:00 AM, on its own Bot
- A routine that checks a Slack channel every 15 minutes
- A group chat of three Bots, used for Monday planning

Answer: A routine that checks a Slack channel every 15 minutes Every 15 minutes is almost 100 runs a day, and every run spends usage.

With the leaks closed, the next thing to get right is the schedule on each routine.

**Next:** [Routines](https://learngrokbot.com/routines)

Turn a job into something that runs on a schedule, at a pace your week can afford.

### Can I see which Bot used the most?

Not in the app. **Usage & Billing** shows one percent for your whole account, with no split by Bot or by routine. To see whether a change helped, watch your usage over a few days at cursor.com/dashboard/usage.

### Can I pick a cheaper model to save usage?

No. Grok Bot has no model picker. Cursor chooses the model for each request.

- 2026-10-06: First published.

## Sources

- [Cursor Help Center: Routines (what to change if usage drops quickly)](https://cursor.com/help/grok-bot/routines)
- [Cursor Help Center: Group chats and Bot-to-Bot messages](https://cursor.com/help/grok-bot/group-chats)
- [Cursor Help Center: Plans and billing (Grok Bot)](https://cursor.com/help/grok-bot/plans)
- [Cursor Help Center: Grok Bot FAQs](https://cursor.com/help/grok-bot/faqs)
- [SpaceXAI docs: Chat and collaboration (group chats)](https://docs.x.ai/grok-bot/chat-and-collaboration)
- [SpaceXAI docs: Bots (what deleting a Bot removes)](https://docs.x.ai/grok-bot/bots)
- [SpaceXAI docs: Skills, routines and automations](https://docs.x.ai/grok-bot/skills-routines-and-automations)
- [SpaceXAI docs: Settings and notifications](https://docs.x.ai/grok-bot/settings-and-notifications)
- [Cursor forum, staff reply: what usage is charged for, and the biggest savings in order](https://forum.cursor.com/t/grok-bot-ultra-users-how-do-you-make-the-weekly-allowance-last-mine-reached-99-in-three-days/171221)
- [Cursor forum, staff reply: fresh chats, quieter handoffs and slower routines](https://forum.cursor.com/t/1-500-in-one-week-running-a-grok-bot-fleet-expected-or-a-bug/172705)
- [Cursor forum, staff reply: how the weekly percent is worked out](https://forum.cursor.com/t/can-cursor-clarify-exactly-which-grok-bot-usage-counts-against-the-weekly-pool-vs-cursor-models-other-models/170951)
- [Cursor forum, staff reply: Bots waking each other](https://forum.cursor.com/t/grok-bot-weekly-usage-hits-100-after-bot-to-bot-reviews-the-user-asked-to-stop/170271)
- [Grok Bot team on X: routines that run too often, 23 August 2026](https://x.com/poteto/status/2091368467060662497)
- [Grok Bot team on X: what group chats cost, 17 September 2026](https://x.com/jediahkatz/status/2100654886513791049)