Claude Code Costs: Seven Changes That Actually Lower the Bill
Claude Code sends project context on every call, so its cost structure looks nothing like chat. What heavy use really costs, and seven changes ordered by how much they save — the first two alone typically halve the bill.
Default to the mid-tier model
This is the single biggest lever and it takes one setting. The mid-tier model handles the large majority of everyday coding — reading code, making scoped edits, writing tests — at roughly a fifth of the frontier model's rate. Escalate deliberately when you hit something genuinely hard, then come back down. Most people who feel Claude Code is expensive have simply never changed the default.
Stop it reading things that do not matter
An ignore file that excludes build output, dependency directories, lock files, and generated assets removes a surprising amount of context from every call. This is pure waste elimination — nothing you want the model to know lives in a build directory. It costs one file and it applies to every call you make afterwards.
Name the files instead of letting it search
When you describe a problem vaguely, the tool explores to find the relevant code, and every step of that exploration is billed. When you name the file and function, it goes straight there. This is the cheapest habit change available and it also makes the output better, because you have already done the part where you know what you want.
Start fresh sessions
Context accumulates across a session, and every call carries all of it. The fiftieth message in a long session can cost many times the first, for the same size of request. When you finish a task, start a new session for the next one. Long sessions feel efficient and are not.
Ask for changes, not essays
Explanation is output, and output is the expensive side of the meter. Telling it to make the change and keep the commentary short is a real saving on a tool used dozens of times a day. Ask for the reasoning when you actually need the reasoning.
Know where your tokens went
Before optimizing further, look at actual usage rather than intuition. People are consistently wrong about which activity dominated their bill — the session that felt expensive often was not, and a routine loop often was. Measure once and you will know which of the six changes above is worth your attention.
Where the savings are
| Change | Typical saving | Effort |
|---|---|---|
| Default to the mid-tier model | 50-60% | One setting |
| Exclude irrelevant directories | 10-30% | One file |
| Name files explicitly | 10-20% | Habit |
| Start fresh sessions | Varies, grows over time | Habit |