[Bug]: CACHE HIT - after cache cold, model change does not work

Abierto
#39,025 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
backend

Línea de trabajo

The issue identifies the affected area as apps/web but names no files or tests. Start by tracing how model changes are passed from the chat interface into the request and how cache hits are handled; the issue reports that the first request after changing from Fable to Haiku still uses Fable, while the next uses Haiku. Done means the first request after a model change uses the selected model and the behavior is covered by a reproducible test.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug needs-triage
Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/web

Steps to reproduce
  1. long night session with fable.
  2. cache cold
  3. tried to change to haiku to compact session
  4. T3 confirmed model changed
  5. Cache hit went to Fable still
T3_Code_(Nightly)_2LSNu0Vtz0 image

Very next message went to Haiku

image
Expected behavior

Effectively change the model and avoid cache hit on the higher model. Btw, the automatic compact did not kick in for some reason in this session

Actual behavior

T3 or easy cli proxy cli will use the same mother model for 1 call and change for the second call

Impact

Minor bug or occasional failure

Version or commit

Latest on 11-18-2026 night

Environment

Windows 11

Logs or stack traces
05:14:18
11/19/2026
claude-haiku-5-5
medium
[email protected]
12••••
Default key
Success
67K
59.4K
7.6K
6.6K
95.42%
56.7K
TTFT
439 ms
Elapsed
33.7 s
225.2 t/s	
$0.004705
05:14:14
claude-haiku-5-5
medium
[email protected]
12••••
Default key
Success
57.2K
56.7K
559
233
56.78%
32.2K
TTFT
768 ms
Elapsed
3.43 s
163.2 t/s	
$0.003664
05:08:55
claude-haiku-5-5
medium
[email protected]
12••••
Default key
Success
62.6K
61.3K
1.3K
641
52.52%
32.2K
TTFT
663 ms
Elapsed
6.66 s
201.7 t/s	
$0.004629
05:08:47
claude-haiku-5-5
medium
[email protected]
12••••
Default key
Success
67.7K
66K
1.6K
989
89.83%
59.3K
TTFT
522 ms
Elapsed
6.9 s
239.0 t/s	
$0.002256
05:08:15
claude-haiku-5-5
medium
[email protected]
12••••
Default key
Success
65.7K
59.3K
6.4K
5.6K
95.59%
56.7K
TTFT
584 ms
Elapsed
31.5 s
204.3 t/s	
$0.004106
05:08:12
claude-haiku-5-5
medium
[email protected]
12••••
Default key
Success
57.1K
56.7K
452
122
56.77%
32.2K
TTFT
604 ms
Elapsed
2.42 s
187.2 t/s	
$0.003611
05:01:40
claude-fable-5-2
medium
[email protected]
12••••
Default key
Success
478.6K
471K
7.5K
0
0.00%
0
TTFT
3.7 s
Elapsed
70.8 s
106.5 t/s	
$9.873244
Screenshots, recordings, or supporting files

EasyCLIProxyAPI_eyKLR580kp.png
T3_Code_(Nightly)_2LSNu0Vtz0.png
EasyCLIProxyAPI_GA9x3q94Qe.png

Workaround

I tried both changing the model on T3 yesterday and it did not work. Attempted to change on the chat using /model and got the same result.

Lenguaje dominante
TypeScript
Estrellas
24.8k
Forks
6.4k
Merge medio
4 h 29 min
PR fusionados (30 d)
488

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de pingdotgg/t3code

Todos los issues de pingdotgg/t3code

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.