Simple rules that stretch your Claude usage limits further every day
10 bite-sized sections
3 min read
Free, no signup
Short answer
A free list of 25 rules to stop hitting Claude usage and token limits in October 2026: how limits work, chats, prompts, files, models and effort, tools and connectors, Projects, Claude Code habits, and API tips.
Claude plans run on a rolling five-hour usage window, and paid plans add weekly limits on top. Each message re-reads your entire conversation, files, tools, and instructions, so context size matters more than how long your question is.
Long, messy chats burn through limits far more than hard questions do.
02
Follow the chat rules
1 · Open a new chat for each new topic
2 · Request a short summary before you switch, and paste only that summary into the new chat
3 · Edit and resend your message instead of tacking on corrections
4 · Bundle related questions into one message
5 · Avoid keeping one chat going for days
03
Follow the prompt rules
6 · Give context once, and give it clearly
7 · Set the length you need, such as “in five bullets”
8 · Add “no preamble” when you just want the answer
9 · Request only the changes, not the full document again
04
Follow the file rules
10 · Share only the pages or sections that matter
11 · Turn large PDFs into text whenever you can
12 · Keep reused files in a Project rather than uploading them again
13 · Clear old or duplicate files out of Projects
05
Follow the model and effort rules
14 · Pick Haiku 5.5 or Sonnet 5.5 for simple tasks
15 · Reserve Opus and Fable for hard problems
16 · Drop the effort level for routine work
17 · Save max effort for the very hardest problems
06
Follow the tool rules
18 · Switch off connectors and web search when a task does not need them
19 · Uninstall plugins and MCP servers you never use
20 · Request a plan before long agent tasks so they stay on track
07
Follow the Claude Code rules
21 · Run /clear between tasks
22 · Run /compact during long sessions
23 · Keep CLAUDE.md lean
24 · Point Claude at exact files with @ rather than asking it to explore
25 · Hand searching and reading to subagents on smaller models
08
Watch your usage
Check usage in Claude’s settings
Try a context meter mod in Claude Code, such as Anthropic’s Token Weather sample
Find the tasks that use the most, and change those habits first
09
Save more as an API user
Turn on prompt caching for long, repeated instructions
Send work that can wait through the Batch API, at lower prices
Cap the maximum output length
Track your spend in the Claude Console
10
Recover when you still hit the limit
Wait for the five-hour window to reset
Move to a smaller model if it still has room
Buy extra usage on a paid plan if you need it right away
Upgrade only if you hit limits every single week
The golden rule
Do not pay for a bigger plan before you fix your habits. Fresh chats, lean files, and the right model stretch any limit.
Fresh chats
Short prompts
Lean files
Right model
Fewer tools
Claude Code
Choose five of these rules and stick to them for one week. Then see how much further your usage stretches.
What does “25 Claude Rules to Stop Hitting Your Token Limits” cover?
It has 10 sections, starting with “Learn how the limits work”, “Follow the chat rules”, “Follow the prompt rules” and “Follow the file rules”, plus 6 more sections.
How long does it take to read?
About 3 minutes. Every section is a short, self-contained card, so you can jump straight to the part you need.
Is this guide free?
Yes. The full guide is free to read on this page, with no sign-up.
For research and ideas only. Results vary and nothing here is a promise of income. See our Disclaimer.
See you Monday!
Weekly newsletter
Everything new, every Monday.
One short email every Monday with everything shipped that week: new free tools and websites, new guides, new free browser tools and what's new in my free Gumroad libraries, plus how the site is growing. Free, and you can unsubscribe anytime.
You sign up on Gumroad, which stores your email to send the newsletter. See our Privacy Policy.
Cookies and your choices
Visits are counted by Cloudflare Web Analytics, which sets no cookies and stores nothing on your device. An affiliate tracking script from Impact.com also loads on our pages and can set its own cookies so partner companies can credit us for sign-ups. Essential storage is always on so pages load and work correctly. You decide whether your browsing preferences are saved on your device. Read the Privacy Policy.