The CLion 2026.2 roadmap is not built around one big headline feature. It is focused on something more practical: reducing the friction around C++ and embedded development.

Debug setup. External sources. CMake target renaming. Zephyr profiles. Live watches.

These are not glamorous problems. But they are the kinds of things that slow teams down every day.

JetBrains notes that this is still a preliminary roadmap, so not every planned item is guaranteed for the final 2026.2 release. But the direction is clear: CLion is becoming easier to configure, easier to inspect and easier to use in complex real-world projects.

Debugging should not start with configuration hunting

One of the most useful planned changes is a new unified debugger configuration workflow.

Today, debugger setup can be spread across toolchains, run/debug configurations, debug servers and DAP debugger settings. For embedded projects, this can get even more complex.

JetBrains plans to introduce a new section, currently called Debug Profile, where local, remote and embedded debugging setups would live in one place. That includes workflows with GDB, LLDB, SEGGER J-Link and ST-Link.

That matters because debugging should start with the problem in the code, not with figuring out where the right setting is.

Better inspection means less manual work

CLion currently shows local variables automatically while debugging, but fields and global variables often require manual watches.

The roadmap includes an option to show fields and global variables directly in the Threads & Variables pane, while keeping them separate from local variables. JetBrains also plans configuration-specific breakpoints, which should help when working with multiple debug sessions, tests or processes.

This is a small but important shift. The IDE should help developers see the state of the program faster, not force them to rebuild the same context manually every time.

Project structure is getting clearer

The roadmap also includes improvements for build tools and project formats.

External sources should get their own node in the Project tool window, which is especially useful when external libraries or Zephyr files share names with files in the root project. JetBrains also plans to add refactoring support for renaming CMake targets across CMakeLists.txt files.

These changes sound simple. But in larger projects, simple navigation and safe renaming can save real time.

Embedded workflows are becoming more practical

For embedded developers, two planned updates stand out.

The first is support for multiple Zephyr West profiles. This should make it easier to manage different build parameters or target different boards in Zephyr West projects.

The second is improved live watches. CLion already supports live monitoring of global variables without stopping program execution. The roadmap extends this to arrays and structs.

That is the kind of improvement embedded teams feel immediately. Less stopping. Less guessing. More visibility into what the system is doing while it runs.

Why this roadmap matters

The CLion 2026.2 roadmap is not about adding complexity. It is about removing it.

For C++ and embedded teams, that is often the difference between a tool that looks powerful and a tool that actually helps during daily work.

If JetBrains delivers on these plans, CLion 2026.2 should make setup, inspection and project navigation cleaner. Not flashy. Just useful.

And for development teams, useful is usually what matters most.