cmd shortcut conflicts with Windows cmd.exe — unusable on Windows

[claell]

Description

The CLI shortcut cmd cannot work on Windows because cmd is already the built-in Windows Command Prompt (cmd.exe). Every Windows machine has cmd in PATH by default, so invoking cmd always opens the Command Prompt instead of Command Code.

The official docs, README, and in-app references all point users to cmd as the primary command. This is misleading for all Windows users.

Environment

• OS: Windows (win32-x64)
• CommandCode version: 0.30.1

Steps to Reproduce

1. Install Command Code on Windows: npm install -g command-code
2. Open any terminal
3. Type cmd and press Enter
4. Expected: Command Code launches
5. Actual: Windows Command Prompt (cmd.exe) opens instead

Impact

• All Windows users (a significant portion of developers) cannot use the documented shortcut
• Docs, README, and in-app help all reference cmd, leading to confusion
• The only working alternative is command-code, which is less discoverable

Suggestion

Either:

1. Rename the CLI shortcut to something that doesn't conflict on Windows (e.g. cc, cde, ccli)
2. Add a platform-specific alias that avoids the conflict on Windows
3. Document the issue prominently in the README and provide the command-code alternative for Windows users

Related

• Possibly related to vscode /ide integration not working #332 (vscode/ide integration not working on Windows)