ak commands install

ak commands install

Install a command

Synopsis

What it does: Resolve a command by <kit>/<command> and copy it into the user-level install location. If the asset declares a runtime block and skill runtime is not opted out, the per-asset env is created via the runtime manager.

Who it's for: Power devs scripting (--yes --json) and users picking from list/search output.

When to use it: After confirming the command exists with ak commands show.

Examples: ak commands install engineer/agent-browser ak commands install engineer/agent-browser --force ak commands install engineer/agent-browser --yes --json

What changes on disk: Writes files under ~/.claude/plugins/<kit>/. Unless AGENTKIT_SKILL_RUNTIME=0, runtime-bearing assets also write ~/.agentkit/skills/<kit>/<name>/ and ~/.agentkit/cache/<hash>/.

Output modes: pretty default on TTY (colors, ASCII markers) plain auto when stdout piped or --no-interactive json --json (single-object envelope, NDJSON-safe)

Exit codes: 0 success 1 runtime error 2 invalid flags 3 user-cancel (SIGINT, prompt-cancel) 5 command not found 6 already installed (re-run with --force)

ak commands install <kit>/<command> [flags]

Options

      --force            Overwrite existing install
  -h, --help             help for install
      --json             Emit machine-readable JSON (implies --no-interactive)
      --no-interactive   Disable interactive prompts (CI-safe)
  -q, --quiet            Suppress non-error output on stderr
  -V, --verbose          Extra diagnostic output on stderr (loses to --quiet)
  -y, --yes              Assume yes for all prompts

SEE ALSO

• ak commands - Per-slash-command management commands