What's New in Rider 2025.2

Explore a new way to code with Junie, an AI coding agent designed to reduce your workload and increase your end-to-end productivity.

We’re building our coding agent with a focus on real-life developer tasks to ensure easier adoption and help you get results you can trust. Junie can execute simple tasks, but it shines when assigned more complex ones. Use Code mode for delegating coding tasks or Ask mode for brainstorming features or new solutions.

Skip to the AI section of this page to read about the latest additions to Junie’s feature set.

Learn more

Rider now supports code completion extensions based on Roslyn’s CompletionProvider API. This means NuGet-delivered analyzers can offer intelligent, context-specific code suggestions by plugging into the Roslyn CompletionService.

This enhancement unlocks support for advanced ASP.NET Core completions (like route patterns and embedded language syntax), as well as custom completions from community packages and in-house tools, bringing greater flexibility to your Rider development experience.

AI Assistant is now available for Microsoft Visual Studio Code, bringing the familiar AI-powered capabilities available in JetBrains IDEs to VS Code workflows.

The extension offers a project-aware chat, intelligent code completions powered by Mellum, documentation generation, commit message suggestions, and more. The newly introduced Agent mode assists with complex, multifile changes, while you maintain full control over the process.

This is a great option if you work with C# in both Rider and VS Code. You can use your current JetBrains AI subscription or, if you don’t have one yet, a free AI EAP license will be issued to you automatically once you log in with your JetBrains Account.

Learn more

This release introduces a great new feature supporting low-level exceptions.

Many frameworks, including Unreal Engine, use the int3 instruction and similar signal or compiler intrinsics to force the debugger to stop, usually implemented as a form of assertion.

Rider 2025.2 allows suppressing these assertion exceptions, either globally through a new exception suppression breakpoint or locally by right-clicking in the editor when a low-level exception occurs.

Read the blog post for more details.

We’ve added a great power user feature with step filters, which changes the behaviour of Step Into for certain methods. If a method or function is marked to be skipped, the Step Into action acts like Step Over, making it much easier to work with “library” code while debugging.

Methods and functions can be added to the UI, or configured through .natstepfilter and .natjmc files.

Debugging multiple processes can be a complex task, so we’ve added a new setting that will pause all processes when a breakpoint is hit in any process, and there are new actions to resume, pause, and stop all processes.

Rider 2025.2 now supports debugging native processes on remote machines, just like it does for debugging remote .NET applications. The Attach to Process dialog will fetch a list of processes from a remote machine via SSH and then attach the debugger to the chosen process.

Currently available for Windows only.

Other minor updates include adding the ability to change the order of child process tabs through the config file that controls attaching to child processes, and we’ve added support for hit count conditions for C++ breakpoints.

Rider now offers source-level debugging for Unity shaders in the bundled Frame Viewer plugin!

• Inspect .rdc rendering snapshots from RenderDoc directly inside Rider.
• Debug draw calls with mapped shader source files.
• Set breakpoints and step through the original ShaderLab source code (not just generated HLSL).
• See active draw calls in a tree view and debug interactively via vertex and pixel selection.
• View and expand textures, and use shaders as context and filters for draw call analysis.

Currently available for Unity projects on Windows only.

A much-requested feature has been the ability to debug both managed and native code, especially in a Unity project. Rider 2025.2 adds support for mixed-mode debugging for Unity projects, so you can now set breakpoints in both C# code and C++ code and step between the two. Use the checkbox in the run configuration editor to enable mixed-mode debugging.

Currently available for Unity projects on Windows only.

We’ve enabled Rider’s integration with the Unity Profiler by default. This feature was introduced as experimental in 2025.1 and has now graduated to being active by default. When you profile in Unity, Rider will automatically load the details and show performance information directly in the editor.

Learn more about this feature from the Rider documentation.

Rider’s excellent support for showing where your code is being used inside Blueprints has been extended to support Blueprints that implement a UINTERFACE.

We’ve added code completion for method names in BlueprintGetter and BlueprintSetter metadata.

In this release, we’ve added a handy little notification to suggest using the .uproject file to load your Unreal Engine project instead of generating a solution file.

Rider can load Unreal Engine’s native project format, and solution file generation isn't required, saving game developers a step. This change also means that Rider can load an Unreal Engine project on Mac and Linux.

Rider 2025.2 bundles a new GDScript plugin, based on the previously community-driven plugin.

This means that Rider can now add its own features for GDScript, such as completion of code, Godot nodes, and resources. It will show documentation tooltips and parameter hints, and it supports Ctrl+Click navigation to declarations and Find Usages, as well as refactorings such as Rename. File templates are included to make it easy to add new source code.

There's also a Scene Preview tool window showing all of the nodes in the current scene and in-editor icons to run the current scene, highlight parent methods, monitor resource usage, connected signals, and more. Inspections can check for problems such as unreachable code, as well as missing or incorrect return types. It can also perform deeper analysis than the Godot editor and can be stricter with untyped values and accidental implicit casts. Additionally, there are a number of Alt+Enter actions to fix issues or make small changes.

We’ll be making more updates to Rider’s GDScript support in future releases.

Rider now provides support for SQL database projects via a bundled plugin. The plugin works out of the box and delivers a smoother experience for working with SQL database projects. Key capabilities include:

• Support for Microsoft.Build.Sql SDK-style projects.
• Project templates for creating new SDK-style SQL database projects.
• Schema comparison.
• Project publishing.
• Importing projects from a database.
• Adding database references.