CLI Overview

Install

Public installs are now thin-bootstrap installs:

# macOS (Homebrew)
brew install kizakicorp/tap/kizaki

# macOS or Linux (direct installer)
curl -fsSL https://get.kizaki.ai/install.sh | sh

The installer places the standalone kizaki binary on disk. The first kizaki init, kizaki dev, kizaki compile, or editor sync flow downloads the exact matching managed runtime into ~/.kizaki/toolchains/<cli-version>/<platform>/ and updates the stable ~/.kizaki/toolchain symlink.

Useful install-health commands:

kizaki version --json
kizaki toolchain status
kizaki toolchain repair
kizaki doctor

Supported public installs today:

• macOS 13+ on arm64 and amd64
• Ubuntu 22.04+ on amd64
• Debian 12+ on amd64

Windows is not part of the public install path yet.

Command Groups

The CLI is organized into five command groups:

• version, toolchain, doctor, init, and dev — install health and local development
• compile and migrate — schema workflows
• deploy, env, secrets, logs — environments and operations
• login, keys, api-keys — access control

Typical Lifecycle

1. Install kizaki
2. kizaki init — scaffold the project
3. kizaki dev — build locally
4. kizaki compile + kizaki migrate — evolve the schema
5. kizaki deploy — ship to staging or production
6. kizaki secrets, env, logs, keys, api-keys — operate in shared environments

The reference pages follow this progression:

• Init and Dev
• Compile and Migrate
• Deploy and Operations
• Auth and Access