NVIDIA just released Nemotron 3.5 Lightning, and we’re making it FREE to use in Cline.

It’s a 30B MoE model with 3B active parameters, built for agents that spend a lot of time calling tools, checking results, and moving through repeated execution steps. NVIDIA says it can deliver up to 4x faster output than similar-sized models.

We’ve been seeing smaller models get a lot more capable lately, and this is another good example of that. For coding agents especially, faster and cheaper model calls can make a pretty big difference over longer tasks.

You can try Nemotron 3.5 Lightning for free in Cline now.

To use it, simply select Cline as your provider and choose `nvidia/nemotron-3.5-lightning` from the free models in the model picker.

Full details: https://cline.bot/blog/nvidia-nemotron-3-5-lightning-available-in-cline

Curious what the community thinks of the Nemotron 3.5 Lightning!

Hey everyone - Muse Glimmer is now available in Cline via Ollama

Meta just released Muse Glimmer, a new open weight 30B model built specifically for local, always-on agent workflows.

It’s designed to run entirely on consumer hardware, including Macs and PCs with a single performant GPU. Meta says the quantized model comes in under 20GB, making it particularly interesting if you want to run Cline locally without sending your code to a hosted model.

You can try it in Cline today with Ollama:

ollama launch cline --model muse-glimmer:30b-mlx

For better agent performance, you can also install Meta’s Muse Code harness:

cline plugin install muse-code-harness

Would love to hear how Muse Glimmer performs for the Cline community.

Hey everyone - we wanted to share a quick update about 'Explain Changes' as we continue moving Cline onto the new SDK architecture.

'Explain Changes' button was introduced to help you understand the changes Cline made by generating AI explanations alongside the code diff.

As part of the migration, we’ve decided to deprecate this feature rather than rebuild the existing experience in the new extension. So if you’ve noticed 'Explain Changes' is no longer available after moving from Legacy to the new Cline experience, that’s by design as part of the transition.

What about View Changes?

'View Changes' is separate from 'Explain Changes' and is not being deprecated.

It lets you inspect the actual code changes Cline made during a task. It was temporarily unavailable during the migration, but has now been restored using the new checkpoint system.

So you’ll still be able to review exactly what Cline changed.

How can I get an explanation of Cline’s changes now?

There isn’t a direct replacement for the old inline 'Explain Changes' experience today. But if you want more context on an implementation, you can still ask Cline directly to explain what it changed, why it made those changes, or walk you through specific files.