Seeing dozens of posts today from people on 5x and 20x plans hitting their five hour limits in under sixty minutes and assuming Anthropic silently slashed quotas. It feels like getting ripped off. There is a very specific mechanical reason your allowance evaporates so fast, and once you look at the token math, you realize eighty percent of your quota is burning on dead weight.
Here is what actually happens under the hood when you give a broad prompt like “fix the bug in the auth flow”:
Turn 1: Claude runs glob and grep tools. It reads 10 to 15 files trying to locate where things are defined. Your session context instantly balloons from 2k tokens to 45k tokens.
Turn 2: Claude makes an edit.
Turn 3: You ask a simple question like “did it pass?”
You think you just sent a tiny request. But the API is stateless. To process that tiny question, Claude Code has to resubmit all 45k tokens from those earlier file dumps.
By Turn 6, you have only asked three or four simple questions, but the harness has processed over 200000 input tokens. That is why your five hour quota is gone before your coffee gets cold. You are paying a compounding token tax on file reads you forgot about twenty minutes ago.
If you want your plan to last through an entire workday without buying extra credits, you have to treat Claude Code as a precision editor rather than a repository search engine:
Never let the agent explore where code lives. Run ripgrep or git grep in your terminal first. Handing Claude src/auth/session.ts lines 40 to 75 takes five seconds and prevents a 40000 token blind crawl.
Feed the failing test or stack trace directly. When the model gets the exact failure point, it fixes the bug immediately instead of inspecting ten unrelated files to guess what broke.
Treat sessions as disposable. The moment a bugfix or feature is committed, run /clear or start a new session. Nursing a conversation across 25 turns and multiple tasks is like carrying an entire project worth of dead logs into every single prompt.
Autonomous repo exploration looks impressive in demos, but it is the single most expensive way to write code with an LLM. Scoping the context yourself takes ten seconds in the terminal, keeps the model fast, and makes standard limits easily survive a full day of heavy shipping.
submitted by
/u/Sweet-Transition-787
Originally posted by u/Sweet-Transition-787 on r/ClaudeCode