Rust code intelligence at a tenth of the memory.
ridx is a language server for Rust that answers from what rustc already worked out. It records definitions, references and types once during cargo check and reads them straight from disk, so your editor gets navigation, hover and completion without a second compiler in RAM.
# as a language server: Zed, VS Code, Neovim, Helix $ ridx lsp no index yet? it builds one, with progress # or ask from the shell $ ridx def . tokio::runtime::Builder $ ridx refs . src/main.rs:12:15 $ ridx hover . src/main.rs:12:15
The compiler already knows the answers
Same editor session, two servers
Each server opened the same 40 files of a repository and answered the same requests: symbols, highlighting, folding, inlay hints, then hover, definition, type definition, highlights, references and completion at sampled positions, and an edit. Memory includes child processes.
What runs where
Two things live in memory: the language server and your unsaved buffers. Everything else is files on disk, mapped on demand. Click any part.
Little-endian, 8-byte aligned, fixed-size records. Lookups are binary searches over sorted tables in mapped memory — nothing is parsed or copied into the heap.
What to know before you switch
One server, every capability your editor asks for
One command, then point your editor at it
Linux (x86_64, arm64) and macOS on Apple Silicon, with rustup. The installer adds Rust 1.98.1, the compiler ridx-driver runs on (your projects keep their own toolchain), checks the release archive's SHA-256 and puts ridx and ridx-driver into ~/.local/bin. Open a Cargo workspace and ridx indexes it on first use; your editor shows the progress.
curl -fsSL https://rust-intelligence.com/install.sh | sh
Prefer to build it? rustup toolchain install 1.98.1 --component rustc-dev,llvm-tools-preview,rust-src, clone the repository and cargo +1.98.1 install --locked --path crates/ridx and --path crates/ridx-driver. If a desktop editor cannot find ridx, give it the full path from which ridx.