Repository navigation
[FEATURE]: show tool usage breakdown in context window #11434
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
We currently have a context breakdown in the Web UI:
I propose adding a similar breakdown for tool calls. In my workflows, most tokens are consumed by tool calls, and I have identified many "inefficient" calls that could be optimized.
Examples of optimization:
Builds: Instructing the LLM to build my project in quiet mode reduced token usage from 15k to 100 tokens.
Jira MCP: I have bloated jira instance, and default attlasian MCP returns A LOT of unrelated things in response. Changing this to self made jira mcp massively reduced token usage.
Proposal:
Add a "Tool Breakdown" section (visualized below) to track which tools consume the most tokens. This visibility will help users refine their instructions to reduce overhead.
Benefits:
Reducing token usage minimizes context rot and generally improves the quality of the model's responses.
Mockup:
Activity
github-actions commentedon Jan 31, 2026
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if your specific request requires tool-specific breakdown beyond general context visibility.
charlesverge commentedon Jun 16, 2026
@podliy16 I've been playing with adding some stats for a similar reason.
Trying a number of different stats options at once, some definition needs to outline what people need to see regularly and how to handle regular usage vs power usage. atm I just have a simple per session addition to the context panel.
Here is my code for now. charlesverge#2
There is tones of pr related to this issue so getting a summary of what folks want. ie cli, api, web and what stats are needed most of the time.
github-actions commentedon Aug 16, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.