Usage & Limits

5 hacks

1.
Use /usage to find which MCP tools and skills burn budget (code.claude.com)
Inspect `/usage` (alias `/cost`) for per-skill, subagent, and MCP breakdowns, then cut the expensive outliers.
0.00 points·13 hours ago·easy·discuss
2.
Start Claude at 7 AM to move your usage reset (docs.anthropic.com)
Schedule an early Claude Code run so your usage window resets around lunch instead of mid-afternoon.
2.00 points·13 hours ago·easy·2 comments
3.
Don't let a long session idle past the one-hour cache lifetime (youtube.com)
Claude Code re-reads your whole conversation at the cached rate. Come back after a long lunch and the first message reprocesses all of it at full price.
0.00 points·13 hours ago·easy·discuss
4.
Run /doctor to trim duplicate CLAUDE.md and unused MCP cost (code.claude.com)
Use the bundled /doctor skill to find duplicate local memory, unused MCP/plugins, and slow hooks eating budget.
0.00 points·13 hours ago·easy·discuss
5.
Enable automatic prompt caching on multi-turn API chats (docs.anthropic.com)
Add a top-level cache_control ephemeral flag so growing conversation prefixes reuse cached tokens and cut API cost and latency.
0.00 points·13 hours ago·intermediate·discuss