Keep hitting Claude’s usage limits.
Turns out… it's not the model.
It is how I am using it.
Turns out Claude doesn’t count messages. It counts tokens.
Once that clicked, everything changed.
Here are 10 things that make a massive difference:
1. Edit your prompt instead of sending follow-ups
If the response is off, don’t send:
“No, I meant…” or “That’s not right…”
Every extra message gets added to history. Claude re-reads ALL of it every time.
Token cost grows fast:
At ~500 tokens per exchange
5 messages = ~7.5K tokens
10 messages = ~27.5K tokens
20 messages = ~105K tokens
30 messages = ~232K tokens
Instead: edit your original prompt and regenerate. You replace the history instead of stacking it.
2. Start a new chat every 15 to 20 messages
Long chats are expensive.
Most tokens get burned re-reading old context, not generating new output.
One dev tracked usage:
98.5% tokens = re-reading history
1.5% = actual output
Fix:
Ask Claude to summarise → copy → start fresh chat → paste summary.
3. Batch your questions
Stop sending multiple messages.
Bad:
“Summarise this”
“Now list points”
“Now give a headline”
Better:
“Summarise this, list key points, and suggest a headline.”
One prompt = one context load.
4. Use Projects for repeat files
Uploading the same file repeatedly = repeated token cost.
Projects cache your files.
Upload once → reuse without re-tokenising.
If you use PDFs, briefs, or docs often, this alone saves a lot.
5. Set Memory and Preferences
If you keep typing:
“Act as…”
“I’m a…”
“I write like…”
You’re wasting tokens every time.
Save it once in settings. Claude remembers it.
6. Turn off unused features
Search, connectors, advanced thinking all add token cost.
If you didn’t intentionally turn it on, turn it off.
7. Use the right model
Not everything needs power.
Haiku → quick, cheap tasks
Sonnet → standard work
Opus → deep thinking
Most people overuse powerful models and burn budget fast.
8. Spread usage across the day
Claude uses a rolling 5-hour window.
If you burn everything in one session, you waste the rest of your day.
Work in blocks: morning, afternoon, evening.
9. Avoid peak hours
Usage limits get hit faster during peak times.
Same work, higher cost.
If possible, run heavier tasks later in the day or on weekends.
10. Turn on overage (if available)
Not for saving tokens, but for safety.
Prevents getting cut off mid-work. You control the spending cap.
Claude doesn’t count messages.
It counts tokens.
Once you start thinking in tokens, not messages, the limits stop being a problem.
6
10 comments
Manda Jackson
7
Keep hitting Claude’s usage limits.
powered by
Skill & Soul Studio
skool.com/skill-soul-studio-7220
Learn simple, AI tools and systems that help you work smarter, stay calm, and grow with ease.
Build your own community
Bring people together around your passion and get paid.
Powered by