macOS
Primary beta path
macOS desktop release
Use the pkg installer for the intended install-time kc setup path. DMG remains a secondary manual beta path.
The current beta ships macOS and Windows desktop installers, CLI wrappers, release metadata, and a measured A/B proof page. The proof is useful because it is concrete, but it is still one controlled run, not a universal benchmark.
Choose the installer that matches your desktop OS. The downloads page keeps the platform-specific kc steps and the current proof status.
Use the pkg installer for the intended install-time kc setup path. DMG remains a secondary manual beta path.
Use the setup EXE as the intended Windows installer path for this beta. MSI is available as a secondary manual path while signing proof remains incomplete.
Download for WindowsRepo A used Claude Code directly. Repo B used Kiwi Control status, guide, graph, pack, and review first. Both runs built the same Markdown Notes Organizer task on the same machine with direct Claude JSON usage data captured from the CLI.
Measured on one controlled greenfield A/B run of the same task using direct Claude JSON usage data. This is useful product proof, not a universal benchmark.
The install guide covers download paths. The command guide covers exactly what to run after that.
curl -fsSL https://kiwi-control.kiwi-ai.in/install.sh | bashirm https://kiwi-control.kiwi-ai.in/install.ps1 | iexkiwi-control --help
kc --help
command -v kcGet-Command kckc init
kc status
kc guide
kc graph build
kc review
kc ui
Kiwi Control keeps authority in the repo, derives structured context in sj-core, exposes it through the kc CLI, and mirrors the same state in the desktop app. Claude Code, Codex, Cursor, and Copilot still do the coding work; Kiwi helps them start from a clearer map.
Token-efficiency is a major product goal, but the claim stays honest: less wandering is plausible because context is narrower and review state is explicit. The measured savings shown here come from one controlled run.
Kiwi Control is designed for desktop-first install where a desktop artifact exists. On macOS the pkg installer is the intended default path for install-time kc setup, with DMG kept as a secondary beta path. On Windows the setup EXE is the intended installer path for the current beta, with MSI available as a secondary manual option.
The standalone CLI wrapper installs kiwi-control and kc only, then verifies kc --help. It does not install the desktop app unless explicitly requested and a real desktop artifact exists.
Public hosting does not equal signing trust. macOS still needs signed/notarized/stapled proof and Windows installers are still unsigned for this beta.
Install/PATH success and release signing trust are separate claims. The proof page and downloads page keep those boundaries explicit.