On this page

Developer CLI on Windows

Use this route for Intel/AMD 64-bit Windows. CoCoCo CLI 0.1.0-beta.12 is a beta release. It installs for your Windows user, with no background service and no WSL requirement. Use your normal Windows account, not a different administrator account.

1. Download and verify the MSI

Download CoCoCo CLI MSI 0.1.0-beta.12 and its checksums. In PowerShell, adjusting the path if needed:

Terminal
Get-FileHash "$env:USERPROFILE\Downloads\cococo-windows-amd64.msi" -Algorithm SHA256

Compare the result with the cococo-windows-amd64.msi line in checksums.txt. They must match; letter case does not matter. Do not install a file whose checksum differs.

2. Install for your user

Close running cococo commands and any editor connection using the CLI. Double-click the MSI in File Explorer and allow it to finish. It uses the standard Windows installation progress window; there is no provisioning-bundle screen.

The installer places cococo.exe in %LOCALAPPDATA%\Programs\cococo and adds that folder to your user PATH. It appears in Settings → Apps → Installed apps. Administrator access is not required.

The MSI is unsigned. If Windows or your organisation blocks it, ask IT to approve the verified download under site policy. Do not disable security protection.

3. Check and connect

Open a new PowerShell window, or restart your editor, then run:

Terminal
cococo --version
Get-Command cococo | Select-Object Source
cococo --help

The version should be cococo 0.1.0-beta.12, and the command should resolve inside your user installation folder. If a different copy is selected, see Updates and existing installations.

Installation does not sign you into a platform or change its configuration. Ask your implementation team for the platform address, environment name and workspace setup instructions. Use your normal account for CLI work. Do not run cococo apply just to test installation: it can change platform configuration.