[Bug] /model sent before the first session is consumed as the first message and reports a switch without opening the picker
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 55/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
- Área
- cli
Línea de trabajo
Start by reproducing the issue in a fresh kimi session and trace how an early /model submission is handled before the first real message. Confirm the intended behavior with the issue’s two options, then verify that the command opens the Select a model picker or returns an explicit error without creating a session or reporting a switch.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
What version of Kimi Code is running?
Observed on 2026-09-15; kimi --version currently reports 2.1.1. Not yet re-verified on 2.1.1.
Which model were you using?
Whatever the fresh session shows in the footer — the failure does not depend on a particular model.
What platform is your computer?
Darwin 27.0.0 arm64 arm
What issue are you seeing?
On a brand-new session the screen says there is no session yet and that one will be created on the first message. Sending /model at that moment does not open "Select a model". The slash text is accepted as the first user message, and the UI then prints a "Switched to ..." line for the current model, which looks like a successful switch. The picker never appeared, so any following filter text is not treated as type-to-search.
What steps can reproduce the bug?
- Start
kimiso the first screen is an empty session (no prior conversation in that terminal). - Before any normal chat message, submit the line
/model. - Expected: a picker titled
Select a model. - Observed: no picker; a "Switched to " line appears and the session now exists.
What is the expected behavior?
/model is a slash command. Before the first real message it should open the model picker, or be rejected with an error saying slash commands are not available yet. It should not create the session and should not print a switch confirmation for a picker that never opened.
Additional information
Waiting until the composer is clearly ready and then sending /model does open the picker — the problem is specific to the early submit.
Possibly related: #3830 (settings in a new-session draft not reaching the first turn) — same "before the session exists" window, different symptom.
- Lenguaje dominante
- TypeScript
- Estrellas
- 7.5k
- Forks
- 1.2k
- Merge medio
- 12 h 45 min
- PR fusionados (30 d)
- 329
Preparar el entorno
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de MoonshotAI/kimi-code
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
MoonshotAI/kimi-code#4010 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
MoonshotAI/kimi-code#4008 ·
Los mantenedores suelen responder en 1 día
-
docs(zh): configuration/providers.md is missing the "OAuth and credential injection" sectionAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 92/100
MoonshotAI/kimi-code#3947 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
MoonshotAI/kimi-code#3836 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
MoonshotAI/kimi-code#3790 ·
Los mantenedores suelen responder en 1 día
Todos los issues de MoonshotAI/kimi-code
Issues similares
-
Resources: New palettes of MacaoAbiertoresources
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
railmapgen/rmg-palette#2445 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
danielmiessler/LifeOS#2242 ·
Los mantenedores suelen responder en 5 días
-
good first issue hacktoberfest help wanted translation
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
callstackincubator/appduct#129 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 88/100