analyzed is a drop-in replacement for rust-analyzer that runs analysis through a shared daemon.

A normal rust-analyzer process loads the standard library, dependency crates, and inferred types for each editor session. Much of that work is identical across projects on the same toolchain. analyzed keeps the shared state in one daemon, so compatible sessions can reuse the same loaded crates and analysis data instead of building their own copies.

Installation

cargo binstall analyzed

We plan to add official packages for scoop, homebrew, and nixpkgs after the project has been used for a while and has enough stars.

Or from a checkout:

cargo install --path crates/analyzed

Usage

Point your editor's rust-analyzer path at analyzed. It uses LSP over stdio, as rust-analyzer does. The first connection starts the daemon in the background.

analyzed status              # daemon state, as JSON
analyzed stop
analyzed daemon --foreground # run in the current terminal

Sharing

Sessions share a backend when their toolchain and Cargo configuration match. Each session keeps its own workspace view, so different roots and nested projects can use the same shared world when their load settings are compatible. Unsaved edits stay private to the session that made them, and other sessions see the on-disk version until the buffer is saved. Each session runs the upstream rust-analyzer main loop, so editor behavior stays the same as rust-analyzer.

How it works

Before compiling, the build takes the ra_ap_* packages selected by Cargo, applies the project patches, and emits the bridge crates used by analyzed. Each release targets one upstream version, reports that version, and passes the upstream test suites, including the LSP end-to-end tests.

License

MIT OR Apache-2.0, same as rust-analyzer.