JetBrains shipped RustRover 2026.2 today with the feature axum developers have been quietly asking for: the IDE now understands your routes. Route-to-handler navigation, URL resolution, and endpoint discovery are live — ending the era of grep-searching your own codebase to find which function handles /api/users/:id.
Axum Gets First-Class IDE Support
The headline addition is framework intelligence for axum, Rust’s fastest-growing web framework and the backbone of the Tokio ecosystem’s web stack. Before today, axum routes were plain strings to the IDE — you could write router.route("/users/:id", get(get_user)) and the IDE would do nothing special with it. If you wanted to know what handler was registered for a route in a large service, you searched by hand.
RustRover 2026.2 changes that with four specific capabilities:
- URL resolution — Resolve a URL path to its registered handler directly.
- Endpoint discovery — See all routes across a project without reading router setup code.
- Route-to-handler navigation — Click a route string, jump to the handler function.
- Inlay hints — See which handler is attached to a route inline, without opening another file.
This is what IntelliJ users have had for Spring controllers for years. Rust web development has been serious enough to power Discord’s backend and Cloudflare’s edge services — the IDE tooling is now catching up to the actual usage. For teams with 30 or 40 routes spread across multiple router files, endpoint discovery alone will save real time.
reqwest Joins the Party
The second framework addition is reqwest, the HTTP client that has accumulated over 306 million downloads on crates.io and sits in virtually every Rust project that touches the network. RustRover 2026.2 adds generation assistance for reqwest client calls and navigation between call sites and related handlers.
This is table stakes that has been missing. Writing a reqwest call has been pure text editing — no generation help, no navigation, no contextual assistance. If you forget the exact signature for sending a JSON body, you were reaching for the docs. That changes with this release.
Ferrocene Toolchain Support: The Quiet Big Deal
The third major addition will matter less to web developers and a great deal to anyone building Rust for safety-critical systems. RustRover 2026.2 adds first-class support for Ferrocene, the qualified Rust toolchain from Ferrous Systems certified for ISO 26262 (ASIL-D, automotive) and IEC 61508 (SIL4, industrial).
Ferrocene toolchains are installed via criticalup rather than rustup. RustRover 2026.2 now detects criticalup-managed toolchains and delivers full code insight — completions, inspections, navigation, code analysis — on qualified builds. Ferrocene 26.02.0 expanded its certified function set from 2,903 to 5,169 functions earlier this year, and Rust adoption in automotive and industrial systems is accelerating under EU Cyber Resilience Act pressure. Until today, those developers were using Rust tooling that did not know about their toolchain. Now they have an IDE that does.
AI Tooling Gets More Seamless
Two AI additions round out the release. GitHub Copilot is now natively integrated in RustRover via a direct JetBrains and Microsoft partnership — previously it required the ACP Registry setup. It is now out of the box.
The Agent Skills Registry is also new: install framework-specific knowledge once, and AI agents in RustRover carry that context across every project and session. You can pull skills from public GitHub repositories or import the skills you have already configured in Claude Code or Codex, so you are not re-explaining your axum conventions every time you open a new chat window.
How to Get RustRover 2026.2
RustRover 2026.2 is available now via the JetBrains blog or through the IDE’s built-in updater. If you are on an active subscription or using the free tier, the update is ready. The 2025 State of Rust Survey found nearly half of companies now use Rust in production — the IDE tooling is finally pulling even with where those deployments have been for years.
The axum route navigation is what most developers will notice on day one. The Ferrocene support is quieter but signals something larger: Rust’s tooling ecosystem is maturing across the full spectrum of where Rust is actually being deployed — not just web services, but the safety-critical systems that increasingly depend on it.
