Microsoft Releases TokenEconomizer: Coding Agents Spend 18.4–30.9% Less Money
A coding agent re-learns the project and loads unneeded tool descriptions at the start of every session, and you pay for those tokens. Microsoft's free TokenEconomizer plugin stores facts about the project and stops loading what isn't needed. On SWE-Bench, where agents fix real bugs, costs fell 18.4–30.9% across five agent-and-model combinations. If you hit usage limits quickly, try the plugin on your own repository.
AI-processed from X: @TechScopeAR; edited by Hamidun News
Anyone who works with coding agents often knows the feeling: the plan limit runs out by midweek, and the API bill grows faster than the number of closed tasks. A significant share of the spending is repetition. The agent opens a new session and again figures out how the project is structured, where the tests live, and which package manager is used.
It also loads tool descriptions you don't need. All of this is paid for in tokens, the small pieces of text the model provider counts. Microsoft has released TokenEconomizer, a free plugin, as open source, and it removes exactly these repetitions.
According to the authors, on SWE-Bench, a popular benchmark where agents fix real bugs in open-source projects, the cost of the work dropped by 18.4–30.9%.
Put simply: for every $100 in spending, you get $18–31 back on the same tasks.
What TokenEconomizer does
It is an open-source plugin. It is compatible with Claude Code, Codex, Copilot CLI, and Pi, so it is not tied to a single ecosystem. The subtitle of the GitHub repository reads "Experience-Driven Black-Box Cost Control for Coding Agents." "Black box" here means the tool operates from the outside and does not require rewriting the agent itself.
The approach rests on three mechanisms, according to the project description:
- The plugin learns from past sessions in your project and stores information about it. The agent doesn't have to rediscover it every time.
- It stops loading tool definitions you don't use. Each such definition takes up space in the context and is paid for on every request.
- As a result, each request carries fewer tokens.
A everyday analogy: a new team member asks at every morning standup where things are in the repository. You can keep paying for those explanations over and over, or you can give them notes. TokenEconomizer tries to keep such notes automatically.
What the measurements showed
The authors report results on SWE-Bench. Costs fell 18.4–30.9% across five different agent and model configurations. The spread is wide: in one combination the savings are under a fifth, in another nearly a third. So the actual gain depends on which agent and which model you use.
For scale: if a team spends, say, $1,000 a month on agents, 18–31% savings means roughly $180–310 saved on the same tasks. For a solo developer on a subscription, the benefit looks different: limits are consumed more slowly, and you can keep working longer without a pause.
Limitations and what to do
There are several fair caveats. First, the figures were published by the authors themselves, and there are no independent checks yet. Second, SWE-Bench involves fixing bugs in well-known repositories. Your closed monorepo with a non-standard build may produce different results. Third, the available description does not show how the "experience" is actually stored: where the notes live, how they are updated, and what happens when the project changes significantly. Stale memory can be worse than no memory, so this needs watching.
The practical takeaways:
- If you are running into the limits of Claude Code, Codex, or Copilot CLI, install the plugin on one non-critical project and compare token usage over a week with your usual baseline.
- Track quality as well as cost: the share of solved tasks should not drop. Savings that you pay for with errors are worth nothing.
- Check the repository to see what data the plugin stores about your project. For commercial code, this is a question of security policy.
- If you have many connected MCP servers and tools, the effect of dropping unneeded definitions will likely be more noticeable.
The news is telling in its own right: the cost of working with coding agents is gradually becoming a separate engineering problem. Previously it was addressed by choosing a cheaper model. Now tools are appearing that save on repeated context without changing either the model or the agent. For teams where the token bill is already a noticeable line in the budget, this is a reason to include such a check in routine tool evaluation.
- Nov 21, 2026Applied Digital Asks Oracle and Meta for Billions in Power Guarantees
- Nov 21, 2026Microsoft Releases Seven MAI Models: Coding Model Delivers 98% of GPT-6.1 Sol's Quality at 40% of the Price
- Nov 21, 2026GitHub Copilot now lets teams share plugins by default
- Nov 21, 2026LanceDB Raises $57.5M for a Database That Trains Models on Video and Images
Key Questions Answered
What TokenEconomizer does?
It is an open-source plugin. It is compatible with Claude Code, Codex, Copilot CLI, and Pi, so it is not tied to a single ecosystem. The subtitle of the GitHub repository reads "Experience-Driven Black-Box Cost Control for Coding Agents." "Black box" here means the tool operates from the outside and does not require rewriting the agent itself. The approach rests on three mechanisms, according to the project description: The plugin learns from past sessions in your project and stores information about it.
What the measurements showed?
The authors report results on SWE-Bench. Costs fell 18.4–30.9% across five different agent and model configurations. The spread is wide: in one combination the savings are under a fifth, in another nearly a third. So the actual gain depends on which agent and which model you use. For scale: if a team spends, say, $1,000 a month on agents, 18–31% savings means roughly $180–310 saved on the same tasks.
What are the key details on Limitations and what to do?
There are several fair caveats. First, the figures were published by the authors themselves, and there are no independent checks yet. Second, SWE-Bench involves fixing bugs in well-known repositories. Your closed monorepo with a non-standard build may produce different results. Third, the available description does not show how the "experience" is actually stored: where the notes live, how they are updated, and what happens when the project changes significantly.
Build & Ship Production AI Agents Without Boilerplate Code
Start your free 72-hour trial at Hamidun Academy (academy.hamidun.com) — interactive lessons on Claude Code & Cursor, live Tech Radar, and production agent templates.
The AI world, distilled — once a week
Seven stories that actually mattered, hand-picked. No noise, no reposts, no press releases.
Done! Check your inbox for a confirmation.