Command guide

Run Kiwi Control without guessing what comes next.

`kiwi-control` and `kc` point to the same CLI. Most people use `kc` for daily work. Start with the install verify commands, then run the first repo flow below.

Install first Open downloads Troubleshooting

Verify install

kiwi-control --help
kc --help

Then verify that `kc` is actually on your path.

command -v kc
Windows PowerShell:
Get-Command kc

First repo flow

cd /path/to/repo
kc init
kc status
kc guide
kc graph build
kc pack status
kc review
kc check
kc ui

Already initialized repo

cd /path/to/repo
kc status
kc guide
kc graph status
kc graph build
kc pack status
kc review
kc check
kc ui
What to run

Core commands

kc initInitialize the repo-local Kiwi contract when a repo is not set up yet.
kc statusShow current repo state, readiness, and the next recommended action.
kc guideShow what to read or run next for the current repo and task shape.
kc graph statusShow graph freshness and repo-intelligence status.
kc graph buildRefresh the repo-intelligence artifacts.
kc pack statusShow the active pack guidance and capability lane.
kc reviewBuild review-oriented guidance from repo state and current diff.
kc checkValidate the repo-local contract and workflow assumptions.
kc uiLaunch or attach to the Kiwi desktop app.
kc nextAsk Kiwi for the next useful action in the current repo state.
kc validateRun task-oriented validation flow for the current repo state.
kc checkpoint "ready for review"Record a milestone before handoff or push discussion.
JSON-first

Use these when another agent needs structured output.

kc status --json
kc guide --json
kc graph build --json
kc pack status --json
kc review --json
kc check --json

These are the cleanest starting points before deeper Claude Code, Codex, or Cursor work.

Desktop vs CLI

The app and the CLI are related, but not identical.

The desktop app is the recommended path when you want the full Kiwi surface.
The wrapper installers install the CLI bundle only by default.
If the desktop app is already installed, kc ui can launch or attach to it.
You do not need the CLI for basic desktop-only usage.
With coding agents

How to use Kiwi with Claude Code, Codex, or Cursor.

1. Install Kiwi Control.
2. Run kc status, kc guide, kc graph build, and kc review.
3. Start the coding-agent work from that repo state instead of raw repo exploration.
Troubleshooting

Fix the common install and first-run problems fast.

`kc` command not found

Open a fresh terminal or fresh PowerShell window first. If `kc` is still missing, run the wrapper install again from the install page.

Desktop app installed but CLI missing

The desktop app and CLI are separate install surfaces. The wrapper install is the clean fallback when terminal command setup did not complete.

Windows PATH not refreshed yet

Close the current PowerShell window, open a fresh one, then run Get-Command kc and kc --help.

macOS first-open trust warning

That is a beta trust warning, not proof of installer trust. Control-click the pkg and choose Open, or use System Settings > Privacy & Security and choose Open Anyway.

What is the difference between `kiwi-control` and `kc`?

They point to the same CLI. `kiwi-control` is the full name. `kc` is the short alias.

Next step

Install, verify, then open a repo.

The install page covers the exact download and wrapper paths. This page covers what to run right after that.

Open install guide Open downloads Support