[FEATURE]: show tool usage breakdown in context window #8119

Open
opened 2026-02-16 18:09:12 -05:00 by yindo · 1 comment
Owner

Originally created by @podliy16 on GitHub (Jan 31, 2026).

Originally assigned to: @adamdotdevin on GitHub.

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:
Image

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:
Image

Originally created by @podliy16 on GitHub (Jan 31, 2026). Originally assigned to: @adamdotdevin on GitHub. ### Feature hasn't been suggested before. - [x] 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: <img width="672" height="165" alt="Image" src="https://github.com/user-attachments/assets/ed261a61-e2e3-499d-9dee-e839d288321d" /> 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: <img width="665" height="202" alt="Image" src="https://github.com/user-attachments/assets/ed1c06c2-f591-4942-8eb9-5fef2216c06e" />
yindo added the discussionweb labels 2026-02-16 18:09:12 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 31, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #6152: Session context usage (similar to /context in Claude) - proposes a TUI dialog showing context window breakdown
  • #10575: Add /context command to display session token usage - requests visibility of token usage details
  • #5555: Session-specific stats command and exit summary - proposes session statistics with token usage breakdown
  • #10354: Near-Real-Time Token and Cost Visibility - requests live token consumption display with cost details

Feel free to ignore if your specific request requires tool-specific breakdown beyond general context visibility.

@github-actions[bot] commented on GitHub (Jan 31, 2026): This issue might be a duplicate of existing issues. Please check: - #6152: Session context usage (similar to /context in Claude) - proposes a TUI dialog showing context window breakdown - #10575: Add /context command to display session token usage - requests visibility of token usage details - #5555: Session-specific stats command and exit summary - proposes session statistics with token usage breakdown - #10354: Near-Real-Time Token and Cost Visibility - requests live token consumption display with cost details Feel free to ignore if your specific request requires tool-specific breakdown beyond general context visibility.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8119