Feature Description
Currently, the Usage section shows overall token consumption, but it doesn't provide a breakdown by model.
It would be very helpful to include per-model token usage (input, output, and total tokens) so users can:
- Identify which models are consuming the most tokens.
- Better estimate and optimize costs.
- Compare usage across different models.
- Debug unexpected token spikes from specific models or workflows.
This would be especially useful for users who frequently switch between multiple models or providers within the same project.
Use Case
No response
Additional Context
No response
How important is this to you?
Nice to have
Feature Description
Currently, the Usage section shows overall token consumption, but it doesn't provide a breakdown by model.
It would be very helpful to include per-model token usage (input, output, and total tokens) so users can:
This would be especially useful for users who frequently switch between multiple models or providers within the same project.
Use Case
No response
Additional Context
No response
How important is this to you?
Nice to have