Cargo Tools gives VS Code a control panel for Rust workspaces (2026)

The Rust extension Cargo Tools adds a project and task layer beside rust-analyzer. It puts profiles, packages, targets, workspace actions, cargo-make tasks, and Cargo aliases into views and shortcuts, so you spend less time rebuilding long command lines. The trade-off is setup: the extension expects a recent VS Code and a working Rust/Cargo installation. 1

The latest GitHub release is v0.6.0, published July 28, 2026. That release hides feature controls when a package has no explicit Cargo features and adds publication to Open VSX. 2

At a glance

Field	Details
Plugin	Cargo Tools — extension ID `NickelWenzel.cargo-tools`. 1
Language / use case	Rust and Cargo project control: profiles, packages, targets, workspace actions, cargo-make tasks, and Cargo aliases. The extension complements rust-analyzer. 1
Current release	`v0.6.0`, published July 28, 2026. 2
VS Code support	VS Code `1.102.0` or newer. 1
Cost / license	Free, MIT licensed. 1
Prerequisites	A Rust toolchain with Cargo installed through rustup, with `cargo` on `PATH` or configured through `cargoTools.cargoCommand`. 3
Adoption signal	The retrieved Marketplace listing does not show a download or rating count. The public release record confirms a recent `v0.6.0` release, so a one-workspace trial is the right confidence test. 1 2
Install	Install Cargo Tools from Visual Studio Marketplace

What it adds beside rust-analyzer

rust-analyzer already supplies the language intelligence most Rust developers expect. Cargo Tools works at the project-control layer: the extension gives you a visual view of the workspace and a consistent place to launch Cargo actions. 1

The Configuration view keeps the active profile, package, and target selections together. The extension can also expose build, run, benchmark, documentation, target-installation, and cleanup actions from that view. 1

The Project Outline view turns a workspace into a tree of members, packages, and targets. You can filter the tree by package name or target type, then build, run, debug, test, or clean the selected scope. 1

The Tasks view collects cargo-make tasks from Makefile.toml and Cargo aliases from .cargo/config.toml. You can filter those tasks, pin the ones you use most, and reach pinned entries with Ctrl+Alt+1 through Ctrl+Alt+5. 3

Cargo Tools Project Outline shows a Rust workspace tree with eight targets beside an open Rust source file in VS Code. — *The official Project Outline demonstration shows the workspace tree, target count, task sections, and the editor in one VS Code window. 4*

That division gives Cargo Tools a narrower job than a Rust language server. The extension helps you choose what to run and where to run it; rust-analyzer continues to handle completion, navigation, and code analysis.

A first workflow: build one target, then run one task

Use a Rust project that already contains a Cargo.toml. Cargo Tools activates automatically when VS Code detects that file in the open workspace. 3

A small workspace gives the panel enough structure to test. For example, this layout contains a library, a binary, and an integration test:

rust-demo/
├── Cargo.toml
├── src/
│   ├── lib.rs
│   └── main.rs
└── tests/
    └── smoke.rs

Open the rust-demo folder rather than the src folder. Then follow this loop:

Open the Cargo Tools icon in the Activity Bar.
In Configuration, choose the dev profile and the binary target.
Press F7 to build the selected target.
Press Ctrl+Shift+F5 to run it, or press Shift+F5 to start a debug session.
Open Project Outline, select the library or integration-test target, and run the same actions against that target.

Cargo Tools documents these shortcuts and the first-project sequence in its getting-started guide. 3

The workflow becomes more useful when the repository already has a team task file. Put the repository's routine check, test, or packaging command in Makefile.toml, then open Tasks and pin the task you run every day. A later press of Ctrl+Alt+1 through Ctrl+Alt+5 takes you straight to the pinned entries. Cargo Tools reads those tasks from the project and keeps the selection visible next to the source tree. 3

The first trial should answer one practical question: does selecting a package and target in the sidebar feel faster and safer than switching between several terminal commands? A multi-crate workspace with a test target gives that question a real answer within one editing session.

Compatibility and sharp edges

Cargo Tools expects VS Code 1.102.0 or newer, a Rust toolchain installed through rustup, and a cargo executable available on PATH. The extension also exposes cargoTools.cargoCommand when the project uses a custom Cargo location. 1 3

The extension is most useful when a project has more than one package, target, feature, or recurring task. A single small crate with one cargo run command leaves less for the sidebar to organize. That is a fit test rather than a defect: the extension's value grows with the number of choices a workspace makes you remember.

Cargo Tools also sits alongside your existing Rust extensions. The Marketplace describes it as a complement to rust-analyzer, so the trial should focus on project navigation and command selection instead of expecting a second language server. 1

The v0.6.0 release changed how feature controls appear: packages without explicit Cargo features no longer show irrelevant controls, and the All features option appears only when multiple explicit features exist. 2

Install or skip?

Install Cargo Tools in one Rust workspace when you regularly move between packages, targets, profiles, or repository tasks. Open the workspace, select a target, build it with F7, run it with Ctrl+Shift+F5, and pin one recurring task. Keep rust-analyzer in place for code intelligence.

Skip it when your Rust projects have one target and a short, stable command loop, or when a terminal-first workflow already gives you the same control with less friction. The direct test is small: compare one multi-crate workspace session, then keep the extension only if the target and task views save you repeated command selection.

Install Cargo Tools from Visual Studio Marketplace or read the official getting-started documentation before trying it in a larger repository.