Getting started

Choose a native download for the quickest start. If you already have a .NET 10 SDK, you can also install Cockpit as a global .NET tool.

Choose how to run

	Native application	.NET tool
Requires	No installed .NET runtime or SDK	.NET 10 SDK
Get it from	GitHub Releases	NuGet.org via the CLI
Start it with	`dotnet-cockpit` executable	`dotnet cockpit`

Node.js is only needed to build the project, never to run a download.

Open the latest release and download the archive matching your operating system and processor. Choose Apple Silicon or Intel on macOS.
Extract the archive.
In a terminal, change to the workspace you want to inspect and launch the extracted executable. Use its full path if it is in another folder.

On macOS or Linux, from the extracted folder:

./dotnet-cockpit

On Windows, run dotnet-cockpit.exe. Cockpit selects an available local port and opens your browser.

Tip

The directory where you launch Cockpit determines its local tool scope. Start it from your project folder to inspect that project’s tool manifest.

To choose a port and open the browser yourself:

./dotnet-cockpit --no-browser --port 5230

Then open 127.0.0.1:5230. Stop Cockpit with Ctrl+C in its terminal.

With a .NET 10 SDK installed:

dotnet tool install --global dotnet-cockpit
dotnet cockpit

dotnet-cockpit is also available as a direct command. To update:

dotnet tool update --global dotnet-cockpit

Overview: review the active SDK, environment health and suggested actions.
Versions: inspect SDKs and runtimes, their paths and support status. Use Install .NET for official installers.
Tools: check global packages and local manifest declarations for your startup directory.
Settings: choose your appearance and configure removal support if you need it.

What you see	What to check
No .NET host found	The native app can start without .NET. Install a host if you want an inventory, then restart Cockpit.
Unexpected SDKs or runtimes	Cockpit uses its inherited `PATH`. Check `dotnet --list-sdks` and `dotnet --list-runtimes` in the launching terminal.
Unexpected local tools	Check the startup directory and any inherited parent manifest.
Unknown support status	The release catalog may be unavailable. Refresh when connectivity returns.
A query failed	Read the reported error; a failed query does not mean the scope is empty.

For details about local scope and changes, read Privacy and safety.