GAME HARNESS KIT
Download
the kit.
Get the CLI, SDK and documentation for your release. Downloads require approved SDK access.
Sign in to download the SDK
Sign in with your GitHub account.
DOWNLOADS
Your available releases
SDK LICENSE
Review before downloading.
AFTER YOU DOWNLOAD
Install
the CLI.
The CLI carries the SDK and prepares its runtime. No separate Bun installation is needed.
one kit, guided setup
- 01
Verify your download
In the kit directory:
shasum -a 256 -c SHA256SUMSon macOS orsha256sum -c SHA256SUMSon Linux. Check the release notes before upgrading. - 02
Install your platform's CLI
Copy it onto
PATHasgame-harnessand make it executable. On macOS, verify its checksum before removing quarantine; see the full instructions. - 03
Run game-harness
Run
game-harnessfor guided setup. It installs the embedded SDK when you create a game. Connect your existing agent with the kit documentation or our agent guide.
Install the Game Harness kit
The kit contains platform CLIs, the SDK archive, a documentation archive, SHA256SUMS and release.json. Keep these release records with your download. Check the release notes before upgrading an existing game.
1. Verify the kit
In the kit directory, run shasum -a 256 -c SHA256SUMS on macOS or sha256sum -c SHA256SUMS on Linux. Every file you have must report OK. If you downloaded only your platform's files, add --ignore-missing.
2. Install your platform's CLI
Choose game-harness-<version>-macos-arm64 for Apple silicon, game-harness-<version>-linux-x64 for Linux x64, or game-harness-<version>-linux-arm64 for Linux arm64. Copy it onto your PATH as game-harness and make it executable. For example, on macOS (replace <version> with the downloaded version):
mkdir -p ~/.local/bin
cp game-harness-<version>-macos-arm64 ~/.local/bin/game-harness
chmod +x ~/.local/bin/game-harness
On Linux, substitute your platform's filename. If ~/.local/bin is absent from echo $PATH, add export PATH="$HOME/.local/bin:$PATH" to ~/.zshrc on macOS or ~/.bashrc on Linux, then open a new terminal.
macOS Gatekeeper
The CLI has an ad hoc signature and is not notarized. macOS may block a browser download because its developer cannot be verified. After the checksum matches, remove quarantine from your installed copy:
xattr -d com.apple.quarantine ~/.local/bin/game-harness
If the attribute does not exist, nothing else is needed. The first launch can pause for several seconds while macOS checks the file.
3. Start Game Harness
Check game-harness --version against the kit version and read game-harness --help. Then run game-harness for guided setup and choose Start a game, or Open Studio from an existing game's directory.
The CLI prepares its embedded SDK and downloads and verifies its private Bun runtime on first use, which needs internet access. You do not need to install Bun separately. Game creation installs the release's SDK dependency for you.
Full instructions and agents
Extract the kit's documentation archive and open package/index.md. The full install guide is package/book/start/install.md; package/book/start/connect-your-agent.md explains how to connect your existing agent. The live agent guide describes verified CLI preparation through the optional account MCP.
Existing projects and SDK-only archives
An SDK archive alone is a developer dependency. Get the matching CLI from the same release for guided setup. For an existing managed game, follow its repository's setup command and reviewed runtime lock; keep its dependency and lockfile changes together.