# Install Combos CLI

Current release: **v1.8.0**. This page, both installers, all binaries and the bundled `combos-cli` skill are maintained and published together.

## One-command installation

macOS or Linux, in bash, zsh or sh:

```sh
curl -fsSL https://cdn.combos.fun/cli/install.sh | sh && . "$HOME/.local/share/combos/env"
```

Windows, in PowerShell 5.1 or newer (no administrator required):

```powershell
[Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Tls12; irm https://cdn.combos.fun/cli/install.ps1 | iex
```

Both commands detect the native platform, download the matching binary, verify SHA256, configure user PATH and install the matching shared skill and connect detected agents. They can be rerun to update CLI and skill together. No Go, Node.js or MCP server is required. macOS/Linux need curl (or download the script with wget) and sha256sum or shasum. Windows downloads require HTTPS access; the installer enables TLS 1.2 for older PowerShell sessions.

Supported binaries:

| OS | Architectures |
| --- | --- |
| macOS | Apple Silicon arm64, Intel x86_64 / amd64 |
| Windows | x86 32-bit, x86_64 / amd64, arm64 |
| Linux | x86 32-bit, x86_64 / amd64, arm64, ARMv7, riscv64 |

Minimum OS: macOS 12+, Windows 10 / Server 2016+, and Linux kernel 3.2+ (some architectures require newer kernels). x86 32-bit builds require SSE2. See the [Go runtime platform requirements](https://go.dev/wiki/MinimumRequirements).

Rosetta and Windows emulation select the native OS architecture. ARMv6, 32-bit macOS and other combinations are unsupported; the installer reports an error. Linux builds have no glibc dependency.

## Verify and sign in

```sh
combos --version
combos skill status
combos skill show
combos account status
# If not signed in:
combos account login
combos account status
```

On this computer, `account login` opens a temporary localhost page. It checks the browser, lets the CLI create a risk session, and then continues to Auth0; the final callback returns directly to the CLI, so no device code is needed. The user signs in or confirms the account. Wait for the command to finish, then confirm the account and credits with `account status`. SSH/headless environments use device login automatically. When the browser is on another computer, use `combos account login --no-browser` and present its device URL and code to the user. `--device` also selects that flow if local callback ports are unavailable. Never request, read out or send tokens or callback authorization codes. After `combos account logout`, the next local browser login asks the user to sign in again. Other browser apps remain signed in; Google or another identity provider may reuse its own session. A successful login clears this preference, while cancellation or failure preserves it. For device login after logout, open the displayed link in a private browser window. Installation does not create paid assets or publish a Post.

## Agent installation procedure

1. Detect the OS, architecture and shell. Run the appropriate command above. Use a user-local install; no administrator privileges are needed.
2. A tool subprocess cannot change its parent's PATH. Source the POSIX env file in each existing shell that needs it, or call the absolute binary path below. New interactive shells load the configured PATH. In fish, run `fish -c 'curl -fsSL https://cdn.combos.fun/cli/install.sh | sh'` then `source ~/.config/fish/conf.d/combos.fish` (use `$XDG_CONFIG_HOME` if set).
3. The default skill destination is `~/.agents/skills/combos-cli`. The installer detects 75 supported agents and connects those found on this machine; agents that read the shared directory use it directly, and others receive a symlink or managed copy. `combos skill agents` lists the support matrix. If the current agent is not detected, run `combos skill install --agent AGENT_ID`. Unknown/custom environments can use `COMBOS_SKILL_DIR` or `--dir PATH`. Preserve user-modified files.
4. Verify `combos --version` returns `v1.8.0`, and `combos skill status --json` returns `data.status: current` (add `--dir PATH` for a custom skill directory). Read `combos skill show` so this task can use the skill immediately. Future tasks may need the agent to reload its skills.
5. Check `account status`, initiate browser login only when required, wait for the user, and verify the account and credits. Installation checks cover the CLI, skill and account; generate paid assets or publish a game only as part of the user's requested task.
6. Follow the welcome guidance in `combos skill show`. Use the user's language and verified state. If they only asked to install, briefly confirm success, explain that you can help build games, generate assets and publish to Combos, and end with concrete examples such as “Publish this game to Combos.” If they already asked you to build, update or publish a game, continue that task after setup instead of stopping at an installation report. If sign-in or setup is still pending, give the actual next step before describing the account as ready.

Default locations:

| Item | macOS / Linux | Windows |
| --- | --- | --- |
| Executable | `~/.local/bin/combos` | `%LOCALAPPDATA%\Combos\bin\combos.exe` |
| Skill | `~/.agents/skills/combos-cli` | `%USERPROFILE%\.agents\skills\combos-cli` |

Set `COMBOS_INSTALL_DIR` to an absolute directory to change the binary location; set `COMBOS_SKILL_DIR` to change the full skill destination. Keep `COMBOS_SKILL_DIR` set for later skill checks, updates, and notices, or pass `--dir PATH` to skill commands and `--skill-dir PATH` to setup/update. Custom directory mode installs only to that directory and cannot be combined with `--agent`. A modified/unmanaged skill is preserved; read `combos skill show` immediately, then back up and merge your changes or choose another directory. In POSIX pipelines export these variables before invoking the command, so they reach the `sh` process. `combos setup` can repair PATH and install the bundled skill offline. Managed, unmodified legacy Codex skills are migrated to the shared version; custom CODEX_HOME, CLAUDE_CONFIG_DIR and XDG_CONFIG_HOME locations are respected. Existing unmanaged or edited skills and linked shell profiles are preserved; resolve the reported conflict or choose a different skill destination before rerunning.

## Agent connections

Common supported agents include Codex, Claude Code, Cursor, Qoder/Qoder CN, Gemini CLI, GitHub Copilot, OpenCode, Windsurf, Trae/Trae CN, Kimi Code, Qwen Code, Cline, Roo Code, Kiro, Amp, Augment, Continue, OpenClaw, Hermes, Droid, Goose, Pi and Zed. Run `combos skill agents` for all 75 IDs, detection results and directories.

```sh
combos setup                                  # PATH, shared skill, detected agents
combos skill install --agent claude-code,codex # explicitly connect these agents
combos skill status                           # shared skill and detected connections
combos skill show references/posts.md          # read instructions in this task
```

No agent detected: the shared skill is still installed, and `combos skill show` works immediately. Detection checks configuration paths rather than starting agent applications. `--agent all` explicitly creates connections for every supported agent; the default leaves undetected agents alone. If symlinks are unavailable (for example, Windows without Developer Mode), managed copies are installed and kept in sync. Installation verifies files and connections, not whether a running agent has reloaded its skill index.

## Updates and first use

`combos update --check` checks for a newer version. Rerun the installation command to update both CLI and skill. Starting with v1.3.0, `combos update` also synchronizes the skill and connects newly detected agents, even if the binary is already current. When upgrading from v1.2.1 or earlier, rerun the installer or run `combos setup` after the old updater completes. Normal account, asset and Post commands show occasional update/skill notices; they do not install files automatically.

After installation and login, you can tell your agent:

- “Publish this game to Combos.”
- “Make a pixel-art runner and publish it to Combos.”
- “Generate assets for my game.”

Your agent builds the H5 locally, generates assets with Combos, prepares a cover and creates a playable Post. Static image generation defaults to Qwen Image 3 Pro (`qwen-image-3-pro`); `--model` selects another model, and `asset generate --schema` shows availability for your account. The cover is required on create and optional on update. Continue an existing game through `combos post get` / `combos post update`; no Project or separate publish command is needed.

Version-pinned installers: [POSIX](https://cdn.combos.fun/cli/v1.8.0/install.sh), [PowerShell](https://cdn.combos.fun/cli/v1.8.0/install.ps1). The immutable version directory includes all binaries, `combos-cli-skill.zip`, signed `release.json` and `SHA256SUMS`.