Rider

Rider 2026.2 comes with:

• Agent skills that connect AI agents to Rider's own intelligence in .NET and game development.
• Support for official Microsoft .NET, Aspire, and Azure Agent Skills directly from the IDE.
• GitHub Copilot now natively built in and available out of the box.
• Faster .NET workflows: ~2.8s quicker debugger launch on Windows, 2–3× faster branch switching in Roslyn solutions, and 7–8% lower backend memory use.
• Faster Unreal Engine projects: ~2× faster C++ and asset indexing when opening the generated .sln.
• WPF Hot Reload for editing XAML while the app runs.
• Redesigned NuGet tool window
• File-based C# app templates.
• Intention previews to see quick-fix and context-action changes before applying them.
• New Game Development category in the New Project dialog, with ready-made Godot and CMake templates plus preconfigured build settings and run configurations.
• Better UE navigation: UInterface implementation tracking and Gameplay Tag usages surfaced in Blueprints via Code Vision and Find Usages.
• Professional Godot support: configurable GDScript formatter, drag scene nodes into code, Autoload/UID resolution, and the official Rider integration addon on the Godot Asset Store.
• Natvis support on Linux and macOS, including godot-cpp.natvis, plus ISPC language support.
• TypeScript 7 support for faster large-codebase workflows.
• Built-in Azure Functions support and Azure DevOps pull requests. For the full list of updates included in this release, click here.

Rider 2026.1.4 comes with the following updates: GitHub Copilot as an integrated agent Rider 2026.1.4 adds support for GitHub Copilot as an integrated agent in AI Chat. Copilot is now available directly from the agent picker, with no ACP Registry setup required. To use it, open AI Chat, select GitHub Copilot from the agent picker, and follow the OAuth login flow to connect your GitHub account. A separate GitHub Copilot subscription is required. The integration also includes a dedicated model picker and support for Copilot CLI slash commands in AI Chat. Learn more from this blog post. For the complete list of changes included in this update, please see our release notes.

Rider 2026.1.3 is out with the following changes: Wayland support on Linux Rider 2026.1.3 brings native Wayland support to Linux users in supported desktop configurations. This update follows the broader rollout of Wayland support, and brings Rider in line with the rest of the IntelliJ-based IDE family. When running in a Wayland-capable environment, Rider can now use the native Wayland toolkit instead of running as an X application. X11 remains supported, and users who need to switch back can still do so via custom VM options. Fixes for MAUI development This build resolves a range of MAUI and Android build, deployment, and debugging issues. Fixes address failures in evaluating deployment properties, uploading APKs, and building across .NET 9 and .NET 10 targets, along with several problems that prevented reliable Android debugging. Key issues resolved:

• RIDER-137704 Deployment properties can now be evaluated when deploying or building MAUI Android apps.
• RIDER-132927 Debugging in the Android Emulator no longer fails to start with a "Failed to parse Activity Name" error.
• RIDER-132740 Resolved a failure when uploading the application APK file to the device.
• RIDER-135767 MAUI .NET 10 Android deployment no longer breaks when adding the net10.0 target framework for unit testing.
• RIDER-137441 MAUI apps now build correctly even with the ReSharper Build option disabled, addressing a missing 'net9.0' target in project.assets.json.
• RIDER-137742 Addressed another case where the application APK file failed to upload to the device.
• RIDER-136581 Running .NET 10 MAUI Android Release builds directly from Rider no longer crashes the app on launch due to missing symbols.
• RIDER-138412 Restored the ability to debug Android apps. For the complete list of issues resolved, please see our release notes.

Rider 2026.1.2 is out with the following changes: Package Manager Console access update In Rider 2026.1.2, the Package Manager Console tab has been removed from the NuGet tool window. The functionality remains fully available via the predefined Package Manager Console session in the Terminal tool window. When we introduced NuGet PowerShell support in Rider 2026.1, we offered it in two places and planned to carry forward only one. Based on usage data and product fit, the Terminal workflow won. All NuGet PowerShell commands, including Entity Framework Core commands like Add-Migration, Update-Database, and Scaffold-DbContext, are available from the Terminal tool window. For the full list of changes, please refer to the release notes.

Rider 2025.3.4.1 is out with the following changes: SSI support in the built-in web server has been disabled. For more details, refer to our release notes.

Rider 2026.1.1 is now available. Here are some notable fixes included in this update:

• The Rider MCP get_file_problems tool now returns file problems correctly. [RIDER-136651]
• Syntax highlighting in source-generated *_g.cs files now works correctly. [RIDER-137702]
• Suppressed warnings no longer appear in Solution-Wide Analysis results. [RIDER-130314] For the complete list of issues resolved, please see our release notes.

Rider 2026.1.0.1 comes with the following fixes: In the recent 2026.1 release, native Wayland support in Rider was prematurely enabled by default on Linux. This caused compatibility issues that prevented several key UI elements such as the Monitoring and dotMemory tool windows from rendering correctly. We are now temporarily disabling Wayland support to restore your full access to all monitoring and profiling tools while we continue to finalize our native Wayland support.

Rider 2026.1 comes with:

• ACP Registry for discovering and installing AI agents.
• Git worktrees support for working with multiple branches in parallel.
• Faster solution loading, more responsive code completion, and lower IDE overhead.
• Enhancements to C# 14 support, including improved inspections and quick-fixes.
• Improved F# debugging with Smart Step Into and return value inspection.
• Support for file-based C# programs without requiring a project file.
• NuGet Package Manager Console (Preview).
• Viewer for .NET disassemblies inside the IDE.
• Built-in Azure DevOps integration for cloning repositories.
• Improved .NET MAUI iOS workflow from Windows.
• Full mobile development support for Unreal Engine on Android and iOS.
• Much faster Unreal Engine debugging and improved Blueprint support.
• Beta support for CMake-based C++ projects.
• Redesigned Unity Profiler integration with timeline and code navigation.
• .NET mixed-mode debugging on Windows.
• Enhanced Godot integration with automatic editor configuration.
• AI-powered database workflows with natural language queries. For the full list of updates included in this release, click here.

Rider 2025.3.4 comes with the following fixes:

• Solutions with projects targeting netstandard2.0 and referenced by other projects now build correctly without NETSDK1005 errors. [RIDER-135258]
• Editor responsiveness during typing has been improved when using AI Assistant, eliminating freezes that could occur during code edits. [LLM-25757]
• Perforce local changes are now refreshed reliably in large projects and no longer hang indefinitely in the Local Changes view. [IJPL-236557]
• Pressing Enter in F# script files now inserts a new line without delay. [RIDER-135197]
• Memory usage during Dynamic Program Analysis has been reduced for long-running sessions. [RIDER-135097] For the complete list of issues resolved, please see our issue tracker.

Rider 2025.3.3 is out with the following changes: Solutions with netstandard2.0 dependency project references now build successfully. [RIDER-135258] .NET MAUI applications can now be deployed repeatedly to Android devices and emulators without failing with "Failed to upload application APK file to device.". [RIDER-132740] MCP project-related tools now correctly return NuGet dependencies, project references, modules, and problems for .NET projects. [RIDER-128984] Navigation actions now correctly position the editor on the target symbol without unexpected scrolling. [RIDER-133722] In .NET 10 applications, the debugger no longer breaks at BreakForUserUnhandledException when exception breakpoints are disabled. [RIDER-132775] For the complete list of issues resolved, please see our issue tracker.

Rider 2025.3.2 is out with the following changes: Agent Client Protocol (ACP) agent registry support You can now browse and install ACP-compatible AI agents directly from a curated registry in the AI Chat tool window. ACP defines a standard protocol for AI coding agents, letting Rider connect to any compatible agent without custom integrations. Users can add agents from the registry and use them immediately in AI Chat. More information in this blog post. Notable fixes:

• Plugin suggestions based on project dependencies are shown again. [RIDER-134557]
• Go to Implementation and Ctrl+Click navigation no longer scrolls the editor to an unexpected position after opening the target file. [RIDER-133722]
• Remove (Ctrl+X) in the Find tool window now removes the selected entry from the results list again. [RIDER-132377]
• InitializeComponent calls in .NET MAUI projects are no longer incorrectly flagged as errors by code analysis. [RSRP-502255]
• .NET MAUI apps can now be deployed and run on physical Android devices when a RuntimeIdentifier is explicitly specified in the project file. [RIDER-133803]
• Solutions with multi-targeted .NET projects (e.g. MAUI projects targeting both platform-specific and plain .NET frameworks) now build correctly from a clean state, including projects that reference them. [RIDER-132476]
• Hot Reload now works correctly in projects that use the C# interceptors feature. [RIDER-126990]
• Hot Reload now works correctly for Blazor WebAssembly standalone projects targeting .NET 10. [RIDER-133277] To learn more about these and other notable fixes included in this build, please refer to this blog post For the complete list of issues resolved, please see our issue tracker.

Rider 2025.3.1 is out with the following changes: Next edit suggestions (NES) Rider 2025.3.1 introduces next edit suggestions, a major new capability from JetBrains AI Assistant. NES analyzes the edits you make and proposes follow-up changes elsewhere in the file to help keep your code consistent as you work. Suggestions appear inline as you type, much like code completion, and are highlighted in light purple. When updates involve other parts of the file, Rider prompts you to review and apply them. Data sharing for better AI in JetBrains IDEs This update delivers the refined, optional data-sharing functionalitypreviewed earlier this year. Its purpose is to improve the reliability and quality of AI-powered features by learning from real usage patterns, always under your control.

• No data is shared unless you explicitly opt in.
• Organizations manage participation at the admin level.
• Individual users can adjust their preferences at any time.
• For non-commercial users, detailed data sharing is enabled by default, but no information is collected until after the in-IDE notice appears. This build also delivers important bug fixes and addresses several security vulnerabilities. More on these and other changes included in this build in our blog post.

Rider 2025.3.0.4 is out with the following updates: JetBrains AI upgrades

• Native support for Junie and Claude Agentinside the AI Chat window.
• Transparent AI quota tracking inside the IDE
• Bring Your Own Key (coming soon) Game development Rider now provides cloud-powered multi-line code completion for shaders in Unity, Unreal Engine, and Godot projects. For Godot developers, cloud completion suggestions are also available for GDScript files. Working with databases Rider replaces the term query console with query file – because consoles have essentially always been files, and it's time the UI reflected that. We've also simplified the workflow, making it more discoverable and consistent. You can learn more about the change in this post. Learn more about these updates from our blog post. This update also brings a number of bug-fixes and stability improvements, including a fix for excessive memory usage when opening large solutions [RIDER-132952]. For the complete list of resolved issues, please refer to our issue tracker.

Rider 2025.3.0.3 is out with the following updates:

• Automatic package restore now works correctly again. [RIDER-132445]
• Rider now correctly detects the ApplicationId from the Android manifest in .NET MAUI projects. [RIDER-132426]
• Occurrence markers are now shown correctly on the scrollbar again when placing the caret on a symbol in C# code. [RIDER-132306]
• Identifier-under-cursor markers are now shown correctly in the error stripe gutter again. [RIDER-132345]
• Solution-Wide Analysis performance has been restored. Code analysis no longer pauses for several seconds after edits, and highlights update instantly again. [RIDER-132309]
• Find in Files now returns results reliably again. [RIDER-132487]
• A regression in the Blazor editor support that prevented Razor files from loading has been fixed. [RIDER-132327]
• Extension methods from source-only NuGet packages are now recognized correctly in the editor and by InspectCode. [RSRP-502165] For the full list of issues we've resolved in this build, please refer to our issue tracker.

Rider 2025.3.0.2

• Authentication for private Azure DevOps NuGet feeds now works correctly again. [RIDER-132336]
• Rider now correctly uses the user’s installed .NET SDK instead of its own bundled one when compiling projects. [RIDER-131155]
• Automatic import of missing namespaces now works correctly again. [RSRP-502252]
• We’ve fixed false positive analysis warnings for get-only setters in .NET projects. [RSRP-502278]
• Fixed a crash caused by a stack overflow in C# code analysis when resolving overloaded operators. [RSRP-502244]
• Errors caused by missing or incomplete results from source generators have been resolved. Projects using .NET source generators or libraries like Vogen now load and analyze correctly without showing false red code. [RIDER-132269]
• Quick-fixes that rely on Roslyn analyzers now work correctly with the Microsoft.CodeAnalysis.CodeStyle package. [RIDER-132263]
• We’ve also resolved a couple of issues that used to cause long freezes. [RIDER-132136, RIDER-130284] For the full list of issues we’ve resolved in this build, please refer to our issue tracker. If you are upgrading from Rider 2025.2.X, here are the highlights of the 2025.3 release:
• Day-one support for the .NET 10 SDK and comprehensive C# 14 support.
• Noticeably faster startup and performance, with core functionality like code completion, search, and navigation available earlier in the startup process.
• A refreshed UI, with the new Islands theme set as default.
• Automatic ASP.NET and database issue detection in the Monitoring tool.
• Perforce MCP support.
• Game development updates, including initial Unreal Engine mobile development for Android, Unity code in IL Viewer, and typed Dictionary structures for Godot.
• Improved support for native/C++ code, including highlighting in inactive preprocessor branches and debugging of constexpr code.
• A smoother experience when working with OpenTelemetry traces. For the full list of updates included in this release, click here.