Install

Kaeonix is distributed as a single self-contained binary of roughly 12 MB. There is no runtime to install alongside it — no Node, no Python, no container. Every installer also links kx to the same binary, so the short form works everywhere the long one does.

Linux

The script detects your architecture (x64 or ARM64), drops the binary in a user-writable location, and puts it on your PATH. No root required.

macOS

Homebrew is the shortest path and keeps upgrades in the usual place:

The POSIX install script works equally well if you would rather not use Homebrew:

Windows

Native PowerShell installer:

Direct downloads

For air-gapped machines or CI images that should pin an exact build, grab the asset directly from the release:

On Linux and macOS the asset is the raw binary — mark it executable and move it onto your PATH. On Windows it is a graphical installer, which registers an uninstaller and handles PATH for you; a bare .exe would only run once on double click.

Upgrading

Kaeonix updates itself:

Use --check to report whether an update exists without installing anything — handy in a shell prompt or a CI guard — and --force to reinstall the latest build even if you are already on it.

Homebrew installs should upgrade through Homebrew (brew upgrade kaeonix) so the two do not disagree about which binary is authoritative.

Verifying the install

doctor reports what Kaeonix can actually see: which config files it loaded, which credentials are present, whether MCP servers connect, and — importantly — whether a sandbox backend is available. If it says sandboxing is unavailable, the agent is running unconfined; see Permissions before granting it broad autonomy.