How to Stop Hitting Claude Limits: Treat Each Session Like a Token Budget
One Claude user on r/ClaudeAI was hitting usage limits mid-session almost daily. The common assumption is to upgrade or space out work. But the real culprit was message bloat: dragging every previous message, every pasted file, and every correction chain into the next task like dead weight.
Key insight: treat each session as a budget
Instead of treating Claude like an infinite chat box, scope each session, load only what matters for that specific task, and clear the context when done. This single mental shift eliminated the user's daily limit problems.
Workflow habits
- Before starting a new task, clear the chat and start fresh.
- Only include files and context directly relevant to the current task.
- Finish a session completely before moving to the next task.
The user created an infographic to lock in these habits (attached in the original Reddit post) and a detailed guide on Substack: Stop Hitting Claude Usage Limits.
📖 Read the full source: r/ClaudeAI
👀 See Also
A Two-Step AI Workflow for Legacy Code Modernization
A Reddit post outlines a two-step 'reverse engineering' approach for using AI with legacy code: first extract business logic into a technology-agnostic Business Requirement Document, then use a 'Master Architect' prompt to rebuild from scratch with modern best practices.
Claude Code Agents Don't Automatically Read Project Documentation
When Claude Code dispatches subagents like Sonnet to write code, those agents only see what's explicitly included in their prompt and don't automatically read CLAUDE.md, MEMORY.md, or other project context files unless specifically instructed to do so.
Field Report: Qwen 3.6 27B on an M2 MacBook Pro (32GB) – Painfully Slow but Smart Output
Running Qwen 3.6 27B IQ4_XS on an M2 MacBook Pro with 32GB RAM yields 7.9 t/s initially, degrading to 3.1 t/s at 52k context. Code quality impresses, but memory bandwidth is the bottleneck.
How to disable Claude Code's verb spinner feature
Claude Code includes a default verb spinner that displays whimsical gerunds like 'Seasoning' and 'Crafting' during processing. You can disable it by editing the settings.json file with a blank space in the spinnerVerbs array.