I stopped hitting Claude's usage limits. Here are 10 things I changed. The key insight: Claude doesn't count messages, it counts tokens.

✏️ Tip 1: Edit Your Prompt, Don't Send a Follow-Up

When Claude doesn't get it right, you might be tempted to send "No, I meant..." or "Ugh, that's not what I wanted..." Don't. Every new message stacks onto the conversation history, and Claude re-reads ALL of it every single turn, burning tokens on context that didn't even help you.

The math compounds fast. At ~500 tokens per exchange: 5 messages = 7.5K tokens, 10 messages = 27.5K tokens, 20 messages = 105K tokens, 30 messages = 232K tokens. Message 30 costs 31x more than message 1.

Instead: click Edit on your original message, fix it, and regenerate. The old exchange gets replaced, not stacked. Fix the prompt, don't feed the history.

🆕 Tip 2: Start a Fresh Chat Every 15-20 Messages

Token costs grow with every message. A chat with 100+ messages at ~500 tokens per exchange burns over 2.5 million tokens, and most of it is just re-reading old history. One developer tracked his usage and found that 98.5% of tokens went toward re-reading history, with only 1.5% toward actual output.

When a chat gets long: ask Claude to summarize everything, copy it, open a new chat, and paste it as your first message. Clean slate, same context, fraction of the cost.

📦 Tip 3: Batch Your Questions Into One Message

Three separate prompts = three context loads. One prompt with three tasks = one context load. You save tokens twice: fewer reloads, and you stay further from your limit.

Instead of sending "Summarize this article," then "Now list the main points," then "Now suggest a headline" as separate messages, write: "Summarize this article, list the main points, and suggest a headline." Bonus: the answers are often better because Claude sees the full picture at once. Three questions, one prompt, always.

📁 Tip 4: Upload Recurring Files to Projects

If you upload the same PDF to multiple chats, Claude re-tokenizes it every single time. Use the Projects feature instead. Upload your file once, it gets cached, and every conversation inside that project references it without burning tokens again. If you work with contracts, briefs, style guides, or any long docs, this one change alone could dramatically cut your token spend.

🧠 Tip 5: Set Up Memory and User Preferences

Every new chat without saved context wastes 3-5 messages on setup: your role, your writing style, your preferences. That's tokens burned on repeat. Go to Settings → Memory and User Settings, save your role, communication style, and preferences once, and Claude will apply them automatically to every new chat. No more "Act as a..." at the top of every prompt.