Token Usage Tips for Claude Code

A detailed Reddit post shares hard-won lessons about managing token consumption in Claude Code. The author notes that most token burn comes from setup context, not Claude's answers. Here are the key practices they use and recommend:
Immediate Wins
- Start new chats for unrelated tasks. Every message in a long conversation resends the full history. A 40-message thread burns tokens on context you stopped caring about 20 messages ago.
- Group small questions into one message. Sending three quick follow-ups individually means three full context loads. Combine them to cut overhead.
- Keep
CLAUDE.mdshort and use it as an index. Dumping everything causes Claude to reread it every turn. Instead, point to separate files so only relevant context loads.
Ongoing Habits
- Be precise with file references. Instead of saying 'here's the whole codebase, figure it out,' which can cost 30–50k tokens in exploration, point Claude to the specific function or module that matters.
- Summarize and restart after 15–20 messages. Ask Claude for a quick summary, paste it into a fresh thread. This drops dead context without losing progress.
- Use lighter models for lighter work. Drafting, reformatting, explaining — route these to smaller models. Reserve the heavy model for reasoning-heavy tasks.
The post invites the community to share their own tricks for keeping token usage under control.
📖 Read the full source: r/ClaudeAI
👀 See Also

Save on Claude Code Bills by Routing Planning Tokens to Cheaper Models
A user cut $40 in overage fees by splitting Claude Code workflows: planning steps go to Haiku 3.5, actual edits and decisions stay on Opus/Sonnet. A 30-line wrapper handles routing; setup took ~2 hours.

CLAUDE.md Entries That Disable Opus 4.7’s Human-Pacing Behavior
Three CLAUDE.md directives that suppress Claude 4.7 Opus's break suggestions, time overestimates, and phase-splitting during long coding sessions.

If OpenClaw Still Needs Your Next Prompt, It Is Not Autonomous Yet — A Setup Prompt for Persistent Workflows
Treat OpenClaw as a coordinator, not a chat surface. Use GOALS.md as a shared roadmap, one Codex goal at a time.

How to Prevent CLAUDE.md Rot: Treat Rules Like Code
After 18 months of real-world use, one developer shares four disciplines to keep CLAUDE.md under 100 lines: use it as an index, separate rules from sources, audit on every PR, and delete more than you add.