Deployment Guide
This section explains how to install and start Claude Code, Codex CLI, Codex Desktop, and OpenCode on different platforms. It only covers local installation, version checks, and first launch. Service connection and model-provider configuration are intentionally not included.
Platform Overview
| Tool | Windows | macOS | Linux |
|---|---|---|---|
| Claude Code | Native install and WSL are supported | Supported | Supported |
| Codex CLI | Native PowerShell install and WSL2 are supported | Supported | Supported |
| Codex Desktop | Supported | Supported | No Linux desktop app yet |
| OpenCode | WSL is recommended; Chocolatey, Scoop, npm, and other native paths are available | Supported | Supported |
Before you install
CLI tools need a working terminal. Installing Git is recommended, and Node.js is required when you choose an npm-based install path.
Choose A Tool
FAQ
Command Not Found
Close and reopen the terminal, then run the version check again. If it still fails, make sure the install location is in PATH, or rerun the install command for your platform.
Windows Script Execution Is Blocked
Make sure you are using the command for the shell you opened: PowerShell and CMD commands are different. If PowerShell blocks execution, use the ExecutionPolicy ByPass command in the relevant tool guide or adjust the local policy after confirming the change is appropriate.
CLI Or Desktop?
Choose Claude Code, Codex CLI, or OpenCode when you prefer a terminal-first workflow. Choose Codex Desktop when you want multiple task threads, graphical diff review, and a desktop project workspace.