Feature summary
Add visible running cost information to the GitHub Copilot App session details panel, alongside the existing token and context usage data.
What problem are you trying to solve?
The GitHub Copilot App shows token usage, but it does not show the running cost of those tokens.
For usage-based pricing, token volume alone is not enough to make an informed decision. Users need to understand the financial impact of a session while it is running, not after they have manually calculated it elsewhere.
This is especially important for cost-sensitive workflows, including hobby projects, open source projects, self-funded work, and organisations that need active cost control. Without visible running cost, it is harder to decide whether to continue, stop, reduce scope, switch model, or move work to a local agent.
Proposed solution
Extend the session details panel to show running cost information next to token usage.
The token section should show input and output token totals with their associated running costs on the same line.
Example:
Tokens
↑ 127.8M ($210.00) ↓ 378.4K ($5.60)
Input: 120 × $1.75 = $210.00
Output: 0.4 × $14.00 = $5.60
Add a new row below the context row:
Total Running Cost
$215.60
The values should refresh as the token totals refresh. The model name does not need to be shown if pricing is already determined by the selected model.
Workflow impact
This would help users make cost decisions directly inside the GitHub Copilot App.
Users could decide whether to continue a session, stop an agent, reduce scope, change model, or move the work to a local agent without leaving the app or manually calculating cost.
This would make usage-based Copilot workflows more predictable, especially where hosted agent usage needs to be balanced against a real budget.
Additional context
Feature summary
Add visible running cost information to the GitHub Copilot App session details panel, alongside the existing token and context usage data.
What problem are you trying to solve?
The GitHub Copilot App shows token usage, but it does not show the running cost of those tokens.
For usage-based pricing, token volume alone is not enough to make an informed decision. Users need to understand the financial impact of a session while it is running, not after they have manually calculated it elsewhere.
This is especially important for cost-sensitive workflows, including hobby projects, open source projects, self-funded work, and organisations that need active cost control. Without visible running cost, it is harder to decide whether to continue, stop, reduce scope, switch model, or move work to a local agent.
Proposed solution
Extend the session details panel to show running cost information next to token usage.
The token section should show input and output token totals with their associated running costs on the same line.
Example:
Tokens
↑ 127.8M ($210.00) ↓ 378.4K ($5.60)
Input: 120 × $1.75 = $210.00
Output: 0.4 × $14.00 = $5.60
Add a new row below the context row:
Total Running Cost
$215.60
The values should refresh as the token totals refresh. The model name does not need to be shown if pricing is already determined by the selected model.
Workflow impact
This would help users make cost decisions directly inside the GitHub Copilot App.
Users could decide whether to continue a session, stop an agent, reduce scope, change model, or move the work to a local agent without leaving the app or manually calculating cost.
This would make usage-based Copilot workflows more predictable, especially where hosted agent usage needs to be balanced against a real budget.
Additional context