Two habits that make usage last: batch requests, send words

How this helps you

The same work uses fewer messages and less image reading, so your weekly usage goes further without dropping any jobs.

✦ Try it

New rule for how we work: if I send a few small requests in a row, wait, ask me if there's anything else, then do them all in one go. Don't reply when I only say thanks, ok or similar. If I send a long PDF or a big screenshot and only part of it matters, tell me which part you need so I can send less next time.

Fill in: No placeholders. Paste it as is into each Bot you message often.

What they did

Sharbel A. made a list of seven ways to stretch Grok Bot usage after the limits changed, and two of them are habits anyone can start today. First, every message makes your Bot read through the chat again, so ten small messages cost a lot more than the same ten things in one message. He gave all his Bots one rule: if he sends a few small requests in a row, wait, ask whether there's anything else, then do it all in one go, and don't reply when he says something like thanks or okay, because even that uses usage. Second, images usually cost more to read than plain text. People send full screenshots or long PDFs when they needed one line, so copy the words instead, crop a screenshot to the part that matters, and turn a long PDF into a text file first.

Who it's for: Anyone hitting the weekly usage limit, especially people who chat with their Bots in lots of small messages.

Before you start

Any Bot you message often.

How to try it

Paste the rule below into each Bot you chat with often (or ask your chief of staff to add it to all of them).
When you think of several things, send them as one numbered message instead of one at a time.
Stop sending 'thanks' or 'ok' as separate messages once a job is done.
Before sending a screenshot, ask yourself if the text would do. If so, copy and paste it.
If you need an image, crop it to the part that matters. For a long PDF, ask for the part you need, or turn it into a text file first.

What to expect

You send three quick requests; the Bot replies once: 'Anything else before I start?' You say no, and it does all three in one pass. Your 'thanks' afterwards gets no reply.

Common mistakes

Batching unrelated urgent work. If one request can't wait, send it on its own.
Pasting a full-page screenshot to show one number. Copy the number.
Thinking short replies are free. Sharbel's point is that each message, even a one-word one, makes the Bot reread the chat.

Related tips

A /clean-start skill for long chats: Save the goal, decisions, files and next action to a handoff file, then pick up in a fresh chat.
Five no-small-talk rules for Bots that talk to each other: Paste five rules into each Bot so group chats and handoffs stop filling up with 'got it' and thumbs-up replies.
Make your Bots read websites with a script, not screenshots: One test: 213K tokens by clicking around, 51K with a browser script, almost none with a plain script. Give your Bots the rule.