Kimi Runner

Execute prompts as the Kimi seat through the shared pi-runner implementation. This replaces the previous Cline-backed shim — --provider openrouter --model moonshotai/kimi-k3 is pinned on every invocation, so the seat no longer depends on whichever provider Cline's mutable state happens to point at; the model that answers is always the forwarded Moonshot model, served via OpenRouter.

Default Model

• moonshotai/kimi-k3 — Moonshot's flagship Kimi K3 seat (long-horizon coding, large-codebase understanding, 1M-token context, always-on thinking), pinned as --provider openrouter --model moonshotai/kimi-k3 on every run. There is a single K3 id — no -code/-thinking variants. Override with --model to point the Kimi seat at a different OpenRouter model id.

Prerequisites

• pi CLI installed and in PATH (npm install -g @mariozechner/pi-coding-agent)
• OPENROUTER_API_KEY in the environment (or an OpenRouter credential in Pi's auth store)

Security Model

This skill delegates to pi-runner, so it has the same execution and data sharing model as the Pi wrapper — see ../pi-runner/SKILL.md. Runs are hermetic (no extensions, skills, or AGENTS.md/CLAUDE.md discovery). Analysis roles (every role except implementer) default to read-only mode (only Pi's file-reading tool enabled). Pass --allow-write to opt out, or --no-tools to block tools entirely.

Shared Wrapper Reference