Automatically finds:

• Unregistered .rs files anywhere in src/
• #[cfg(feature = "...")] attributes not declared in [features]
• Files that should be binaries, examples, tests, or benchmarks

Smart filtering:

• Skips helper modules (checks for mod, use, include! statements)
• Only shows truly orphaned files
• No false positives from utility code

Interactive workflow:

1. Detection runs automatically (or via command palette)
2. Classify each unknown file: Binary? Example? Test? Benchmark?
3. Choose to move files to conventional directories
4. One-click Cargo.toml update

File organization:

Follows Rust best practices automatically!

Color-coded modules:

🟢 Green - Well-maintained public API (documented + public)
🔵 Blue - Public modules (part of your API)
🟡 Yellow - Missing documentation
🟠 Orange - Undeclared modules (not in mod statements)
⚪ Default - Private internal modules with docs

Module information:

• Visibility (pub mod vs private)
• Documentation status (/// or //! comments)
• Test presence (#[test], #[cfg(test)])
• Directory vs single-file modules
• Hierarchical structure
• Module counts - Shows direct children count at all nesting levels

Context-aware display:

• When a workspace member is selected, shows only that member's modules
• Automatically switches context when you select different workspace members
• Clear separation of concerns in multi-crate projects

Click any module to open the file instantly!

Color-coded dependencies:

• 🟢 Green text = Latest version (up to date!)
• ⭐ Yellow star icon = Workspace-inherited dependency (v1.0.5)
• � Package icon = Standard dependency with version number shown

Organized by type:

• Production - Runtime dependencies
• Dev - Development/testing dependencies
• Build - Build script dependencies
• Workspace - Shared workspace dependencies

Workspace-inherited dependencies (v1.0.5):

• Dependencies with { workspace = true } display with yellow star icons
• Show correct version numbers resolved from workspace
• Sorted to the top of their category for easy identification
• Tooltip shows "(from workspace)" origin
• Click to navigate to workspace root Cargo.toml

Version change resilience (v1.0.5):

• Selective reversion - Only failed updates revert, successful ones persist
• Duplicate resolution - Automatically removes ambiguous dependency constraints
• Lock file refresh - Cleans Cargo.lock before updates for reliable resolution
• Clear feedback - Shows which dependencies succeeded vs failed

Real-time crates.io integration - Shows latest available versions automatically

Auto-discovers:

• src/lib.rs - Library target ⭐
• src/main.rs - Main binary ⭐
• src/bin/*.rs - Additional binaries
• examples/*.rs - Example programs
• tests/*.rs - Integration tests
• benches/*.rs - Benchmarks
• [lib] section in Cargo.toml - Custom library configurations

Primary targets (⭐):

• Main binary (src/main.rs) and library (src/lib.rs) targets are marked with a star icon
• Auto-selected when no targets are checked
• Keyboard shortcuts work with library-only crates!
• Both receive identical special treatment and features

Color-coded health:

🔵 Blue - Custom location (non-standard path)
🟠 Orange - Incorrect declaration (name/path mismatch)
🔴 Red - Unknown path or unregistered

Features:

• Multi-select for batch builds
• Drag & drop to reclassify unknown targets
• One-click run/build/test/doc
• "Toggle All" for quick selection
• Library target support for cargo build --lib, cargo test --lib, cargo doc --lib

Parses [features] from Cargo.toml:

[features]
default = ["json"]
json = ["serde_json"]
async = ["tokio"]
database = ["sqlx"]

Usage:

• Check features to enable
• Combine multiple features
• See feature dependencies
• Toggle all on/off

Commands use your selections:

cargo build --features json,async,database
cargo test --features json

Click "Mode: Debug" to switch to Release:

• Adds --release to all commands
• Affects build, run, test, bench, doc

Note: Resets to Debug on VS Code restart. Use snapshots to preserve release configurations!

A snapshot stores:

• Build mode (debug/release)
• Checked targets
• Checked features
• Arguments and environment variables
• Workspace context

Auto-created snapshots:

• Binary projects (with src/main.rs) → "main" snapshot
• Library projects (with src/lib.rs) → "lib" snapshot
• Mixed projects (both) → Both snapshots created
• Workspace projects → One per member

Workflow:

1. Configure UI (targets, features, mode)
2. Click [+] in SNAPSHOTS
3. Name it: "dev", "production", "testing"
4. Click to apply/deactivate

Use cases:

• dev → debug, all features, verbose
• production → release, minimal features
• testing → test targets, fixtures enabled
• frontend-dev → specific workspace members

Requires: cargo-watch (extension offers to install)

Watch actions:

• check - Fast compilation check (recommended)
• build - Full build on changes
• run - Run binary on changes (for servers)
• test - Run tests on changes
• clippy - Lint on changes

Usage:

1. Click "Watch: Inactive"
2. Select action
3. Edit any .rs file
4. Auto-runs: cargo watch -x check

Respects all your settings (features, env vars, etc.)!

Features:

• Shows current edition from Cargo.toml (e.g., "Edition: 2021")
• Click to change edition with a dropdown menu
• Automatically fetches available editions from the official Rust Edition Guide
• Future-proof: New editions appear automatically when documented by the Rust team
• Updates Cargo.toml while preserving file formatting

How it works:

• Fetches edition list from https://github.com/rust-lang/edition-guide
• Parses the official documentation to find all available editions
• Falls back to known editions (2015, 2018, 2021, 2024) if offline

How to Use:

1. View current edition at the top of the tree
2. Click "Edition: 2021" to open selector
3. Choose a new edition from the dropdown
4. Cargo.toml updates automatically ✅

Status bar shows:

• Current toolchain (stable/beta/nightly)
• Version number
• Click for details

No more memorizing rustup commands!

• See toolchain info at a glance
• Check for updates visually
• Switch toolchains from UI

Detects workspace structure:

[workspace]
members = ["cli", "api", "core", "utils"]

Two selection modes:

Label Click (Context Selection):

• Click package name → Sets as active context
• Tree updates to show that package's targets/features
• Use when focusing on one crate
• Click again to deselect and return to "all" view (v1.0.5)

Checkbox Click (Build Selection):

• Check packages → Include in build
• Multi-select for combined builds
• Use for building multiple crates

Special "All Members":

• Click → cargo build --workspace (builds everything)
• Check → Same as checking all individually

Visual indicators:

• ⭐ Selected member shows star icon
• Non-root members show relative directory path as description (v1.0.5)
• Right-click member → "View Member's Cargo.toml" (v1.0.1)

Commands:

# Context: core, Checked: core only
cargo build --package core

# Context: api, Checked: api + core
cargo build --package api --package core

# All Members selected
cargo build --workspace

Workspace snapshots remember your context and selections!

Add reusable arguments:

• --verbose
• --port 8080
• --config dev.toml

Check to enable:

cargo run --bin server -- --verbose --port 8080

Defaults included, add your own via [+] button

Common variables:

• RUST_BACKTRACE=1 - Stack traces
• RUST_LOG=debug - Logging level
• DATABASE_URL=... - Test database

Commands:

RUST_BACKTRACE=1 RUST_LOG=debug cargo run

Default commands:

• cargo clippy - Lint
• cargo search <crate> - Search crates
• cargo add <crate> - Add dependency
• cargo tree - Dependency tree
• cargo update - Update dependencies

Add your own:

cargo build --target x86_64-unknown-linux-gnu
cargo test --nocapture
cargo doc --document-private-items --open

Click to execute in terminal!