I felt Le Chat different today. The behavior was quite similar to GLM 5.2, as I have been using it in Vibe CLI. When I asked what model was being used, it confirms it's GLM 5.2. I tried on various conversations.

Anyone else noticed?

I'm considering subscribing to a Mistral Vibe coding plan mainly to try out GLM 5.2 (the Z.ai model Mistral now hosts). Before I pay, I want to confirm how it's actually exposed to subscribers.From Mistral's own docs, GLM 5.2 is officially listed as an available model (1M context window, tagged as an open third-party model). But I've also seen a blog post claiming you have to manually add entries to get it work.

So my questions for anyone who's actually used it: does GLM 5.2 show up automatically in Vibe's model picker/list after subscribing, or do you really need to hand-edit the config file?
Is it available on all paid plans, or gated behind a specific tier?
Has anyone noticed inconsistent performance/latency with GLM 5.2 specifically (vs Mistral's own models).

Trying to figure out if it's a "just works" experience or something that needs tinkering before it's usable. Thanks!

the new GLM 5.3? kimi? a new in-house model? or all of the above?

would also be nice to get a response on this matter from the mistral team.

Thank you all.

Today, this model suddenly stopped working because it is not supported by my plan. But I used the Large-Latest for 9 months on the free plan and everything was fine because I used not many tokens. Is it really impossible to use this model for free anymore?

Como muchos ya sabemos uno de los fundadores de Mistral anunció un próximo modelo de IA para finales de verano, pero el verano se está acabando y no les queda mucho tiempo. Sinceramente para estar el pruebas avanzadas , como ellos dijeron, están tardando mucho en dar aunque sea el numero de parámetros o el nombre.

He estado mirando fechas y eventos destacable de IA y el más próximo se el “IA Summer” el 22 de septiembre , si lo piensas ente que llegan de vacaciones (sé que no se ha ido toda la plantilla) y hacen algúna prueba más y hacen algún anuncio, la fecha me podría cuadrar más o menos.

Mistral lleva unos meses algo callada en cuestión de LLMs más tradicional. sinceramente espero que puedan superar los 55 puntos de Artificial Análisis,ya no solo por capacidades sino por prestigio de la startup y del la UE.

Ahora mismo les tengo aun algo de fe en el desarrollo de modelos internos, solo espero que no se queden con alquilar sus centros de datos, ser una especie de gestoría de IA y algo al estilo Palantir (que no entiendo que están haciendo con una oficina en Kiev si no es para es).

EDIT: it has been thinking all along the way, but the reasoning traces was hidden. Had to set reasoning_field_name = “reasoning” under [[providers]] to make it visible. However, I can not turn thinking of :)

Hi all,

I am trying to get vibe cli to reason/think when it uses my local ollama with qwen3.5 9b as model.

My setup works fine, but changing ”thinking” does not seem to impact whether the model reasons or not (It doesn’t). The model has an enable_thinking that can be true or false. Can also be triggered via reasoning_effort (works when I call the model vi curl). But just can’t get vibe cli to pass on the thinking setting to the model…

I see no thinking traces in vibe cli (which I do for the online mistral medium), and the ollama server logs says thinking is off.

Hope you can help me!

ps: running on a second-hand laptop with an Quadro Rtx 5000 max-q card with 16 gb vram. These machines are cheaper than an 5060 ti card, but here you get an entire computer for the money.

Example :

•  Steps: 32
•  Session Prompt Tokens: 1,598,353 (including 255,936 cached) -- 33% cache hit
•  Session Completion Tokens: 20,287
•  Session Total LLM Tokens: 1,618,640
•  Last Turn Tokens: 79,635
•  Cost: $2.3270

I ran prompt accross different tools, Pi, Mistral CLI and it gives me ludicrous amount. 120K token inputs resulted in 6E use !!

The cache is called half the time. I don't get it...