Session details should include cached tokens
未关闭
Requests and ideas
- 主要语言
- 没有语言数据
- 星标
- 2.1k
- 派生
- 153
- PR 合并指标
- 30 天内没有已合并 PR
描述
### Short summary
_No response_
### Affected version or release
_No response_
### Installation context
_No response_
### What happened?
With UBB, cached input tokens are charged differently and this difference should be reflected in the UI rather than just showing input/output tokens
### Steps to reproduce
_No response_
### Expected behavior
_No response_
### Additional context
_No response_
贡献指南
调研方向
Start by locating the session details UI that displays input and output token counts, then trace how UBB usage data is presented. Verify the change with a session containing cached input tokens; done means the UI distinguishes cached tokens and reflects their different charging treatment.
由索引模型根据 Issue 内容生成。
评估
- 领域
- frontend
- Issue 类型
- 缺陷
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 活跃度
- 冷清
- 描述清晰度
- 基本清楚
- 新手友好度
- 48/100