Before you start

Combos hosts browser-native games. Upload a complete static website, usually in dist. Your output folder may have another name: always pass its actual path. The authoring tool does not change the final delivery format.

Match your project to a route

Project	What to prepare
Existing H5 build	`index.html` and every referenced file
Plain HTML + JavaScript	HTML, JS, CSS, and assets; no compilation required
Vite / Webpack	Static output from the project’s own build command
Unity	The complete native WebGL export
Roblox	Assets and gameplay adapted or reimplemented in a browser engine

Installing Combos CLI requires neither Node.js nor a Unity plugin or SDK. Vite needs its own Node.js environment; Unity needs official Web Build Support.

Know where your files are


my-game/
├── source/
├── dist/
│   ├── index.html
│   └── assets/
├── cover.png
└── combos.json

The project root contains your editable source. ./dist is relative to the terminal’s current directory. Keep cover.png and the generated combos.json in the project root. The latter binds this project to its published game; it is not source code.

In Codex, open the whole project and its terminal, or use a system terminal. Replace the quoted path below with your own; retain quotes around spaces. Confirm that the displayed directory contains dist and cover.png, or build them first.


cd "/path/to/project"
pwd
ls


Set-Location "C:\path\to\project"
Get-Location
Get-ChildItem

Local and cloud workspaces

Codex and Cursor create files in the selected workspace. Ask your Agent for the full project path, build command, output directory, preview address, and a check of the core gameplay before publishing.

A cloud workspace can build and upload where the CLI is installed, or you can download the project and work locally. Its 127.0.0.1 is not your computer’s localhost: use the tool’s preview link or run a local server after downloading. A local preview works only while its server runs; a Combos share link works independently.

Read examples correctly

Commands require the stated environment and working directory. Replace sample paths, titles, covers, and device flags. BoatAttack’s commit and patch, and Ball Game’s coordinates, belong only to those examples. Lua and JavaScript snippets explain source behavior; they are neither terminal commands nor universal migration scripts.

Source: Combos developer integration guide , checked on 2026-10-08 with CLI v1.14.2. Example results refer to the original recorded runs.