Command Code on Windows

Command Code officially supports Unix-based systems like macOS, Linux, and WSL (Windows Subsystem for Linux). Native Windows support is currently in alpha.

Recommended for Windows

The best way to use Command Code on Windows is through WSL. It gives you a full Linux environment where everything works exactly as documented.


PlatformSupport
macOS✅ Fully supported
Linux✅ Fully supported
WSL (Windows Subsystem for Linux)✅ Fully supported
Windows (native)⚠️ Alpha — PowerShell, Windows Terminal and Git Bash

WSL runs a real Linux shell inside Windows. It is the recommended way to use Command Code on Windows to get a stable experience with all features working as expected.

Install WSL

Open PowerShell as Administrator and run:

wsl --install

This installs WSL 2 with Ubuntu by default. Restart your machine when prompted, then open the Ubuntu app from the Start menu to set up your Linux username and password.

Install Command Code inside WSL

Once you are in the WSL shell, install Command Code the same way as on Linux:

Install Command Code in WSL

npm i -g command-code@latest

Verify the install:

cmdc --version

If you prefer to run Command Code directly on Windows without WSL, it works but native Windows support is currently in alpha. You may encounter rough edges.

Install on native Windows

Install Command Code on native Windows

npm i -g command-code@latest

Verify the install

cmdc --version

Run Command Code on Windows

cmdc
Note

Check out the quickstart guide for more details for using Command Code.

Why cmdc works on native Windows

The cmdc alias doesn't conflict with the built-in Windows Command Prompt. On Windows, cmd is a reserved system command. Every terminal (PowerShell, Windows Terminal, Git Bash) intercepts it and launches cmd.exe instead of Command Code. The cmdc alias avoids this conflict entirely.