JetBrains shipped RustRover 2026.3 on November 5, 2026. The release centres on runtime investigation: it makes the debugger and profiler easier to read for people, and it opens the debugger to AI agents through a new MCP server and skill.
Like every other JetBrains IDE in the 2026.3 wave, RustRover also bundles JetBrains Air, where you launch coding agents and check their edits. A native SSH flow for remote projects, automatic crash reporting and several IntelliJ Platform updates complete the picture.
JetBrains Air in RustRover
Air is the agent workspace that now comes with JetBrains IDEs. It supports Junie, Claude Agent, Codex, Gemini, GitHub Copilot, OpenCode and other tools that speak the Agent Client Protocol (ACP), so Rust teams can keep the agent they already use.
A JetBrains AI subscription is not needed, since existing subscriptions and API keys keep working. A free Junie Lite configuration only requires a JetBrains Account. Junie can also talk to local models served through Ollama or LM Studio, which suits teams that cannot send code to a cloud model.
When an agent edits code, Air shows the diff in the context of the surrounding files. You can pin a note to a particular line, and the agent receives that exact location when it makes the next fix.
Agents can now drive the debugger
The most distinctive addition is a debugger MCP server paired with a skill called rustrover-debugger. The skill explains to an agent how to use the server, letting it place breakpoints, step through execution, read variables and evaluate expressions on your behalf.
In practice you describe a bug in plain language and the agent gathers runtime evidence for it. That helps with faults the source and logs hide, like a value that goes wrong only at run time. Because the agent works through the normal RustRover debugger, you can watch the session and step in whenever you like.
Setup lives under Settings, then AI. You switch on the MCP server first, then enable and install the skill, either for RustRover itself or for whichever external agent you prefer.
Clearer debugger and profiler output
Fully qualified Rust paths can make debugger panels hard to scan. RustRover 2026.3 now shortens type names shown under Variables and Watches, and symbol names shown under Frames. This is enabled by default and can be switched off in the settings.
The profiler is friendlier too. Function names in profiling results are now demangled, and Jump to Source opens the matching Rust function instead of failing with a Declaration not found message. Both fixes cover DTrace profiling on macOS as well as perf on Linux.
Remote development and platform updates
Remote projects can now be handled entirely from the IDE. Open an SSH connection to the machine, launch a session there and resume it whenever you return. RustRover now relies on native OpenSSH, so certificate login, hardware keys such as YubiKey and ProxyJump hosts should work as they do in your shell.
The release also inherits several IntelliJ Platform changes:
- Optional sound cues when builds, tests and background tasks finish, plus audio line marks for screen reader users.
- New Git worktrees receive a copy of the local project configuration.
- Installed and Marketplace plugins now share a single page.
- The terminal defaults to the Ghostty emulator and can open tabs inside the editor area.
Error and UI freeze reports are now sent to JetBrains automatically. JetBrains says only technical data is included and that paths, URLs and usernames are stripped first. The feature can be disabled in the settings.
What it means for developers
Debugger access for agents is a meaningful step beyond agents that only read code and run tests. For Rust, where many bugs involve state that changes across async tasks or loops, letting an agent gather breakpoint data can save time on the first round of investigation.
Treat the agent's findings as leads, not answers. Start with a bug you already understand, compare what the agent reports with your own debugging, and keep the session visible so you can take over when it drifts.
The demangled profiler names and working Jump to Source are small but practical fixes for anyone tuning hot paths with perf or DTrace. Teams with strict data policies should check the new automatic reporting option before rolling the update out widely.
How to get RustRover 2026.3
Install the update from inside the IDE or download it from the RustRover page on the JetBrains website. The full What's New page covers the remaining settings and changes.
For more context, see our coverage of CLion 2026.3 and GitHub Copilot in JetBrains Air.
Conclusion
RustRover 2026.3 brings Air to Rust developers and goes further by giving agents real debugger control through MCP. Shorter debugger names, usable profiler results and native SSH remote work make it a worthwhile upgrade even for those who skip the AI features.
Sources
See my articles more often when you search Google.
