JetBrains released ReSharper 2026.3 on November 10, 2026, the same day Microsoft shipped .NET 11 at .NET Conf 2026. The headline change is that the AI Assistant tool window inside Visual Studio now lets developers pick Claude Agent or Codex as a coding agent, next to JetBrains' own Junie.
The update also covers the new C# 15 language features, adds fresh code inspections, and keeps the test runner in step with xUnit v3 4.0 and NUnit 5.0. For .NET teams that live in Visual Studio, it is the release that makes the extension ready for the new runtime.
Claude Agent and Codex Join Junie
ReSharper 2026.2 introduced Junie as the first coding agent in the extension. With 2026.3, the agent list in the AI Assistant window also offers Claude Agent and Codex. Each one can write and change code, run commands in a terminal, or explain parts of a solution without leaving the IDE.
JetBrains connects the two newcomers using ACP, the open Agent Client Protocol that lets editors talk to coding agents. All three agents can also call a ReSharper refactoring skill, so a rename or a move of a type to another namespace runs as a real refactoring instead of a series of file edits.
On first use of either third-party agent, ReSharper requests permission before installing it, because both come from third parties. If Node.js is missing on the machine, ReSharper installs it as well.
Licensing and AI Limits
The AI agents are not free. The key points from the JetBrains FAQ are:
- Claude Agent and Codex need a JetBrains AI subscription and draw on its quota.
- Personal Claude or ChatGPT plans cannot be used, and bring-your-own-key is not supported in this release.
- JetBrains AI Pro trials are no longer offered in ReSharper, although running trials continue until they end.
- Junie Lite, the free tier of Junie, is open to any logged-in JetBrains Account holder, with no ReSharper license required.
- AI features remain restricted in Mainland China.
.NET 11 and C# 15 Support
ReSharper 2026.3 understands the C# 15 syntax that arrived with .NET 11. That includes union types, closed class hierarchies, arguments in collection expressions, extension indexers, and break or continue statements that target a label. Analysis, completion and navigation work with the new code, and new inspections and quick-fixes help move older code to the new forms.
The extension also handles the preview of the memory safety redesign. It recognizes the safe keyword and the new unsafe expression form, and it flags unsafe contexts that are missing or not needed, with fixes for both.
On the decompiler side, runtime-async methods in .NET 11, which the runtime runs directly rather than through compiler-built state machines, now show up as normal async methods. The IL Viewer tags them with the async keyword, and dotPeek 2026.3 gets the same change. Note that runtime-async remains in preview for this .NET release.
Code Analysis and Testing Changes
Several smaller improvements target everyday coding:
- Collection expressions are suggested in more places, such as lists and immutable builders filled by loops, AddRange or single Add calls.
- New inspections spot char values mistakenly used as array sizes or indexes, culture-sensitive calls and implicit string sorting.
- Another check finds using statements that dispose a task rather than the value it returns, and one more prefers tuple syntax over verbose ValueTuple creation.
- Parameter info now groups overloads that start with the same parameters, which makes long lists easier to read.
The unit test runner now handles NUnit 5.0 and version 4.0 of xUnit v3, discovers MSTest 4 tests more reliably, and applies Playwright options like LaunchOptions that are defined in a .runsettings file. Microsoft.Testing.Platform support is now on by default, so frameworks like TUnit work without extra setup.
C++ users get the separate ReSharper C++ 2026.3 changes covered in our earlier story.
What It Means for Developers
The agent choice is the practical win. Developers who run these agents from a command line today can now keep them inside Visual Studio with ReSharper's refactoring engine behind them, which should give safer renames than raw text edits. The catch is billing: usage goes through JetBrains AI quota, not your existing Claude or ChatGPT plan.
For .NET 11 adopters, update the extension before trying union types or closed hierarchies, since older builds will flag the new syntax. The same goes for teams moving to the newest xUnit or NUnit majors. Our coverage of the .NET 11 and C# 15 release explains the language changes in more detail.
How to Get Started
Get the 2026.3 build and keep the AI Assistant component selected during setup. If its window is missing afterwards, open the installer once more and choose the repair option for that component. Then open the window, sign in to a JetBrains Account if asked, and choose an agent from the list.
Developers who prefer a full IDE can look at Rider 2026.3, which shipped with the same day-one .NET 11 support.
Conclusion
ReSharper 2026.3 turns the Visual Studio extension into a multi-agent workspace while keeping pace with .NET 11 and C# 15 from launch day. The language and test runner updates are the must-have part for most teams, and the AI agents are a useful extra for those with a JetBrains AI subscription.
Sources
See my articles more often when you search Google.
