CLion’s Classic Engine Unbundled: What’s Next
Last year, we announced that CLion Nova would become the default C and C++ engine for all users and that all new language improvements would be developed for Nova. With CLion 2026.2, we’re taking the next step in that transition – the legacy Classic engine is moving from the CLion bundle to an optional plugin.
What this means for you
If you already use Nova, no action is required.
If you still need the Classic engine, it’s available as the standalone C/C++ Language Support via Classic Engine plugin. You can install it from Settings | Plugins | Marketplace in CLion or from JetBrains Marketplace. We’d appreciate it if you could also contact the CLion support team and let us know what’s preventing you from adopting Nova.
Transition timeline
If you’re still using the Classic engine, here is the transition timeline:
- CLion 2026.2 (now) – The Classic engine moves from CLion to an optional plugin.
- CLion 2026.3 (November 2026) – The last stable Classic release compatible with the IDE.
- After 2026.3 (December 2026) – Updates end for the Classic engine.
Does your team need help moving to Nova?
If your team depends on Classic-specific behavior or workflows, contact your customer success engineer or account manager. We’ll work with you to understand your roadblocks and plan the transition.
If you’re unsure whom to contact, please use our enterprise customer contact form. You can also contact the CLion support team via email or YouTrack.
