Command Code on Windows

Windows is fully supported, and there are two ways to run Command Code on it.

Recommended

Use WSL if you can. Command Code is built for POSIX environments, as are most of the tools around it, including project scripts, hooks, Makefiles, and CI. WSL gives you a Linux environment with a POSIX shell, so things work as documented without a compatibility layer.

Native Windows is fully supported too, and it is a first-class fallback rather than a lesser one: a real PowerShell tool, Windows-aware path and process handling, and the same session, permission, and taste behavior you get on macOS and Linux. Reach for it when WSL isn't an option - a locked-down machine, a Windows-only toolchain, or a project that has to build against Windows itself.

Supported platforms

Platform	Support
WSL (Windows Subsystem for Linux)	Fully supported - recommended on Windows
Windows (native)	Fully supported - PowerShell, Windows Terminal, Git Bash
macOS	Fully supported
Linux	Fully supported

Install

In WSL (recommended)

Set up WSL first, then install from inside the WSL shell exactly as you would on Linux:

npm i -g command-code@latest

Verify the install, then log in and start a session:

cmd --version
cmd login
cmd