Session details should include cached tokens
Abierto
Requests and ideas
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 2.1k
- Forks
- 153
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
### 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_
Guía de contribución
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Área
- frontend
- Tipo de issue
- Error
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Estado de actividad
- Tranquilo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 48/100