# Introduction
Claude Code is de facto helpful, however it might probably additionally get costly a lot sooner than individuals anticipate. The reason being easy. You aren’t solely paying for the immediate you simply typed. In lots of instances, Claude can be carrying the remainder of the session with it like earlier messages, recordsdata it already learn, device outputs, reminiscence recordsdata like CLAUDE.md, and different background directions. So when token use begins climbing, the actual concern is normally not dangerous prompting. It’s messy context.
A number of generic recommendation on this subject shouldn’t be that useful. “Preserve conversations brief” is true, however it doesn’t inform you what really strikes the needle. What really helps is knowing how Claude Code builds context, what retains getting resent, and which components of your workflow quietly add waste over time. On this article, we are going to take a look at 7 sensible methods that can allow you to to make use of Claude Code effectively with out always worrying about price. So, let’s get began.
# 1. Switching Fashions by Process Complexity
This one is easy however massively under-used. Not each activity wants your costliest setup. On API billing, Opus prices 5x greater than Sonnet per token. On subscription plans, heavier fashions drain your quota window sooner.
/mannequin sonnet # Day-to-day: writing assessments, easy edits,
# explaining code, refactoring
/mannequin opus # Advanced: multi-file structure choices,
# debugging gnarly cross-system points
/mannequin haiku # Fast: lookups, formatting, renaming,
# something repetitive
Begin each session on Sonnet. Solely swap to Opus while you genuinely want deep evaluation or advanced refactoring. Drop to Haiku for the mechanical stuff. You may as well management effort stage instantly with /effort. For simple duties, reducing the hassle stage reduces the considering funds the mannequin allocates, which instantly saves output tokens.
# 2. Holding CLAUDE.md Small and Helpful
Probably the greatest methods to avoid wasting tokens is to cease retyping the identical challenge guidelines in each chat. That’s precisely what CLAUDE.md is for. It hundreds earlier than Claude reads your code, earlier than it reads your activity, earlier than something. It persists within the context window for the whole session and isn’t lazy-loaded or evicted. This implies a 5,000-token CLAUDE.md prices 5,000 tokens on each single flip, whether or not you ship 2 messages or 200. So, put your steady directions there: methods to run assessments, which package deal supervisor to make use of, your formatting guidelines, vital architectural constraints, and the directories Claude ought to keep away from touching. This cuts repeated immediate overhead throughout periods.
One other vital half is to maintain it lean. Don’t paste assembly notes, design historical past, or lengthy implementation guides into it. You’re going to get the perfect outcomes when CLAUDE.md works extra like a lookup desk than an enormous mind dump.
# 3. Delegating Verbose Work to Subagents
This is among the most genuinely useful ideas as a result of it adjustments how context grows. Subagents are remoted Claude situations that run in their very own context window. When a subagent runs, all its verbose output — file searches, log dumps, multi-step reasoning — stays remoted. Solely the abstract returns to your important dialog. This will preserve your important thread a lot cleaner. However that is additionally the place quite a lot of generic recommendation goes mistaken. Subagents usually are not routinely cheaper. Group testing exhibits that for small duties, particularly easy shell actions or fast git operations, a subagent might be wasteful as a result of the structure itself provides overhead via prompts, device definitions, and additional tool-call spherical journeys. So the sensible rule shouldn’t be “use subagents for all the things.” It’s “use subagents when the saved main-context litter is value greater than the startup overhead.”
# 4. Pointing Claude to Precise Information and Line Ranges
One of many quickest methods to waste tokens is to ask Claude to “look across the repo” when the problem actually lives in a single or two recordsdata. The extra obscure the duty, the extra seemingly Claude is to spend tokens opening a number of recordsdata, exploring useless ends, and reconstructing context you can have handed it instantly. Right here is an instance.
Unique:
“Look via the auth code and inform me what’s mistaken.”
Higher:
“Examine
src/auth/session.tstraces 30 to 90 withsrc/api/login.tstraces 10 to 60 and clarify the mismatch.”
The primary one sounds pure, however it typically triggers costly exploration.
One other tip is to use plan mode earlier than costly operations. Toggle it with Shift+Tab. In plan mode, Claude outputs a step-by-step plan with out making any adjustments. You evaluation the plan, lower something pointless, then swap again to regular mode. This eliminates the largest supply of token waste: trial-and-error execution, the place Claude tries issues, hits errors, and iterates — with every iteration costing tokens.
# 5. Utilizing /compact Proactively (Not Reactively)
Claude can compact your session routinely, and you too can run /compact your self. However timing issues greater than individuals assume.
By the point Claude has inspected a number of recordsdata, run instructions, and explored just a few false leads, your session normally accommodates quite a lot of materials that not issues. That’s the proper second to compact. As a substitute of carrying all that additional context into the subsequent step, you shrink the dialog as soon as the vital components are clear, after which proceed with a a lot lighter session.
A standard mistake is utilizing /compact too late. Many builders wait till Claude begins forgetting issues or exhibits a context warning. At that time, the session is already overloaded, and the abstract shouldn’t be as clear or helpful. If you happen to compact earlier, whereas the session remains to be “wholesome,” the abstract is a lot better. You retain the important thing info, drop the noise, and keep away from dragging pointless tokens into each future step.
# 6. Checking /context Earlier than Optimizing
Probably the most underrated concepts is solely what’s consuming context. A number of token waste feels mysterious till you keep in mind that the costly half will not be the seen immediate. It could be a giant file Claude learn earlier, gathered device output, a heavy reminiscence file, or the overhead of additional tooling.
The /context command is your diagnostic device. Earlier than altering your entire workflow, take a look at what is definitely being loaded or repeatedly re-sent. In lots of instances, the largest enchancment doesn’t come from higher prompting. It comes from recognizing one “quiet offender” that has been driving alongside in each flip. For this reason it’s higher to not optimize blindly. First, examine what’s in your context. Then take away or scale back the components which might be really inflicting the bloat.
# 7. Holding Your Tooling Setup Easy
Claude Code can hook up with many exterior instruments and information sources, which is highly effective — however extra linked tooling may imply extra context overhead as soon as these instruments come into play. If too many instruments or helpers are concerned, the mannequin can find yourself dragging round extra overhead than the duty actually wants. Preserve your setup lean. Use integrations that clear up an actual repeated downside. Don’t load up Claude Code with each accessible ability simply because you’ll be able to.
# Remaining Ideas
The easiest way to scale back Claude Code token utilization is to not babysit each immediate. It’s to design your workflow so Claude solely sees what it genuinely wants. The largest wins come from controlling automated context, narrowing search scope, and stopping noisy aspect work from contaminating the primary session.
Cease considering solely about prompts and begin interested by context structure.
Kanwal Mehreen is a machine studying engineer and a technical author with a profound ardour for information science and the intersection of AI with drugs. She co-authored the e-book “Maximizing Productiveness with ChatGPT”. As a Google Technology Scholar 2022 for APAC, she champions range and educational excellence. She’s additionally acknowledged as a Teradata Variety in Tech Scholar, Mitacs Globalink Analysis Scholar, and Harvard WeCode Scholar. Kanwal is an ardent advocate for change, having based FEMCodes to empower ladies in STEM fields.
# Introduction
Claude Code is de facto helpful, however it might probably additionally get costly a lot sooner than individuals anticipate. The reason being easy. You aren’t solely paying for the immediate you simply typed. In lots of instances, Claude can be carrying the remainder of the session with it like earlier messages, recordsdata it already learn, device outputs, reminiscence recordsdata like CLAUDE.md, and different background directions. So when token use begins climbing, the actual concern is normally not dangerous prompting. It’s messy context.
A number of generic recommendation on this subject shouldn’t be that useful. “Preserve conversations brief” is true, however it doesn’t inform you what really strikes the needle. What really helps is knowing how Claude Code builds context, what retains getting resent, and which components of your workflow quietly add waste over time. On this article, we are going to take a look at 7 sensible methods that can allow you to to make use of Claude Code effectively with out always worrying about price. So, let’s get began.
# 1. Switching Fashions by Process Complexity
This one is easy however massively under-used. Not each activity wants your costliest setup. On API billing, Opus prices 5x greater than Sonnet per token. On subscription plans, heavier fashions drain your quota window sooner.
/mannequin sonnet # Day-to-day: writing assessments, easy edits,
# explaining code, refactoring
/mannequin opus # Advanced: multi-file structure choices,
# debugging gnarly cross-system points
/mannequin haiku # Fast: lookups, formatting, renaming,
# something repetitive
Begin each session on Sonnet. Solely swap to Opus while you genuinely want deep evaluation or advanced refactoring. Drop to Haiku for the mechanical stuff. You may as well management effort stage instantly with /effort. For simple duties, reducing the hassle stage reduces the considering funds the mannequin allocates, which instantly saves output tokens.
# 2. Holding CLAUDE.md Small and Helpful
Probably the greatest methods to avoid wasting tokens is to cease retyping the identical challenge guidelines in each chat. That’s precisely what CLAUDE.md is for. It hundreds earlier than Claude reads your code, earlier than it reads your activity, earlier than something. It persists within the context window for the whole session and isn’t lazy-loaded or evicted. This implies a 5,000-token CLAUDE.md prices 5,000 tokens on each single flip, whether or not you ship 2 messages or 200. So, put your steady directions there: methods to run assessments, which package deal supervisor to make use of, your formatting guidelines, vital architectural constraints, and the directories Claude ought to keep away from touching. This cuts repeated immediate overhead throughout periods.
One other vital half is to maintain it lean. Don’t paste assembly notes, design historical past, or lengthy implementation guides into it. You’re going to get the perfect outcomes when CLAUDE.md works extra like a lookup desk than an enormous mind dump.
# 3. Delegating Verbose Work to Subagents
This is among the most genuinely useful ideas as a result of it adjustments how context grows. Subagents are remoted Claude situations that run in their very own context window. When a subagent runs, all its verbose output — file searches, log dumps, multi-step reasoning — stays remoted. Solely the abstract returns to your important dialog. This will preserve your important thread a lot cleaner. However that is additionally the place quite a lot of generic recommendation goes mistaken. Subagents usually are not routinely cheaper. Group testing exhibits that for small duties, particularly easy shell actions or fast git operations, a subagent might be wasteful as a result of the structure itself provides overhead via prompts, device definitions, and additional tool-call spherical journeys. So the sensible rule shouldn’t be “use subagents for all the things.” It’s “use subagents when the saved main-context litter is value greater than the startup overhead.”
# 4. Pointing Claude to Precise Information and Line Ranges
One of many quickest methods to waste tokens is to ask Claude to “look across the repo” when the problem actually lives in a single or two recordsdata. The extra obscure the duty, the extra seemingly Claude is to spend tokens opening a number of recordsdata, exploring useless ends, and reconstructing context you can have handed it instantly. Right here is an instance.
Unique:
“Look via the auth code and inform me what’s mistaken.”
Higher:
“Examine
src/auth/session.tstraces 30 to 90 withsrc/api/login.tstraces 10 to 60 and clarify the mismatch.”
The primary one sounds pure, however it typically triggers costly exploration.
One other tip is to use plan mode earlier than costly operations. Toggle it with Shift+Tab. In plan mode, Claude outputs a step-by-step plan with out making any adjustments. You evaluation the plan, lower something pointless, then swap again to regular mode. This eliminates the largest supply of token waste: trial-and-error execution, the place Claude tries issues, hits errors, and iterates — with every iteration costing tokens.
# 5. Utilizing /compact Proactively (Not Reactively)
Claude can compact your session routinely, and you too can run /compact your self. However timing issues greater than individuals assume.
By the point Claude has inspected a number of recordsdata, run instructions, and explored just a few false leads, your session normally accommodates quite a lot of materials that not issues. That’s the proper second to compact. As a substitute of carrying all that additional context into the subsequent step, you shrink the dialog as soon as the vital components are clear, after which proceed with a a lot lighter session.
A standard mistake is utilizing /compact too late. Many builders wait till Claude begins forgetting issues or exhibits a context warning. At that time, the session is already overloaded, and the abstract shouldn’t be as clear or helpful. If you happen to compact earlier, whereas the session remains to be “wholesome,” the abstract is a lot better. You retain the important thing info, drop the noise, and keep away from dragging pointless tokens into each future step.
# 6. Checking /context Earlier than Optimizing
Probably the most underrated concepts is solely what’s consuming context. A number of token waste feels mysterious till you keep in mind that the costly half will not be the seen immediate. It could be a giant file Claude learn earlier, gathered device output, a heavy reminiscence file, or the overhead of additional tooling.
The /context command is your diagnostic device. Earlier than altering your entire workflow, take a look at what is definitely being loaded or repeatedly re-sent. In lots of instances, the largest enchancment doesn’t come from higher prompting. It comes from recognizing one “quiet offender” that has been driving alongside in each flip. For this reason it’s higher to not optimize blindly. First, examine what’s in your context. Then take away or scale back the components which might be really inflicting the bloat.
# 7. Holding Your Tooling Setup Easy
Claude Code can hook up with many exterior instruments and information sources, which is highly effective — however extra linked tooling may imply extra context overhead as soon as these instruments come into play. If too many instruments or helpers are concerned, the mannequin can find yourself dragging round extra overhead than the duty actually wants. Preserve your setup lean. Use integrations that clear up an actual repeated downside. Don’t load up Claude Code with each accessible ability simply because you’ll be able to.
# Remaining Ideas
The easiest way to scale back Claude Code token utilization is to not babysit each immediate. It’s to design your workflow so Claude solely sees what it genuinely wants. The largest wins come from controlling automated context, narrowing search scope, and stopping noisy aspect work from contaminating the primary session.
Cease considering solely about prompts and begin interested by context structure.
Kanwal Mehreen is a machine studying engineer and a technical author with a profound ardour for information science and the intersection of AI with drugs. She co-authored the e-book “Maximizing Productiveness with ChatGPT”. As a Google Technology Scholar 2022 for APAC, she champions range and educational excellence. She’s additionally acknowledged as a Teradata Variety in Tech Scholar, Mitacs Globalink Analysis Scholar, and Harvard WeCode Scholar. Kanwal is an ardent advocate for change, having based FEMCodes to empower ladies in STEM fields.
