Three Claude Limit Myths, Busted by Claude's Own Docs (and a Prompt That Finds What's Eating Your Limit)
Switching to Sonnet doesn't bring you back from a session limit, /compact isn't free, and a quick question in an old chat costs the whole chat. What the docs say, what to do instead, and a prompt that audits your setup
Claude Code's docs answer three things almost everyone gets wrong about their usage limit. Each myth below quotes the page it comes from, then the habit that actually saves your limit.
Myth 1: switch to Sonnet when you hit your limit
- The docs: "The session and weekly limits are shared across all models, so switching models doesn't restore access."
- So after "You've hit your session limit" or "weekly limit", /model changes nothing. Wait for the reset time in the message.
- The exception: after "You've hit your Opus limit" or "Sonnet limit", switching to a model outside that family keeps you working.
- The cost: each model has its own cache, so the first message after a switch rereads the whole chat with no cache hits. Pick your model at the start of a task.
Myth 2: /compact saves your limit
- The docs: "/compact reads the conversation it summarizes, so compacting a large context is itself a large request."
- "When you want a fresh start instead of continuity, /clear costs nothing."
- Habit: new task = /rename, then /clear. Come back later with /resume.
Free, for your email
Get the full setup steps + the copy-paste setup prompt
The rest of this guide (3 more sections, 1 copy-paste prompt) opens right here. The setup prompt, one paste into Claude that sets it all up, comes by email only. Use your real address.
Unlocks: Myth 3: a quick question is cheap · The catch · Sources
50,000+ follow where these guides come from. No spam, reply “unsubscribe” any time.