kimi

Ask Kimi a read-only question in free-form prose mode.

Cancel an active plugin-managed Kimi job for the current repository.

Verify local Kimi companion readiness and manage review-gate state. Writes a managed PreToolUse hook block to ~/.kimi-code/config.toml so kimi-code enforces this plugin's safety contract.

Run a read-only Kimi challenge review that challenges assumptions and surfaces safer alternatives.

Hand Kimi an objective to pursue AUTONOMOUSLY across multiple turns (experimental goal mode), bounded by a hard wall-clock budget. Write-capable, gated by the same PreToolUse hook as rescue.

Use this agent when the user wants Kimi to answer a free-form question about the repository in prose — explain a module, trace a flow, compare alternatives, or reason about a concept in context. Choose this agent over kimi-review when the user wants a narrative answer rather than diff-focused findings, and over kimi-rescue when the user wants understanding rather than implementation.

Use this agent when Claude wants Kimi to run an adversarial review that challenges the implementation approach, design choices, tradeoffs, and assumptions rather than just flagging defects. Choose this agent when the user wants pushback on whether the chosen approach is the right one, not a tighter pass over implementation defects (see kimi-review for that).

Use this agent ONLY when the user has explicitly asked Kimi to pursue a stated objective AUTONOMOUSLY across multiple turns (experimental goal mode) — a multi-step task the user wants Kimi to drive to completion on its own, not a single bounded edit. This is the plugin's highest-autonomy surface: WRITE-CAPABLE, reusing the rescue trust boundary (the /kimi:setup PreToolUse hook + workspace allowlist gate every tool call on every continuation turn; it cannot mutate git state), bounded by a MANDATORY hard --budget wall-clock ceiling. Requires BOTH an explicit objective AND explicit intent for hands-off autonomous pursuit — do NOT auto-promote a single bounded fix into a goal loop (use kimi-rescue) or a read-only question into one (use kimi-ask / kimi-review / kimi-swarm). Refuses without the hook.

Use this agent proactively when the user wants to delegate a substantial investigation or implementation task to Kimi, especially multi-step bug hunts, cross-file refactors, or work the main Claude thread would rather offload than context-switch through. Choose this agent when the work is too large for an inline response but the user clearly wants it handed off, not just reviewed.

Use this agent when Claude wants an independent second-pair-of-eyes review from Kimi over a working-tree diff or branch diff. Choose this agent for read-only diff review — multi-file changes, design-risk changes, or when the user explicitly asks for another reviewer. Not for implementation work (see kimi-rescue) or free-form Q&A (see kimi-ask).

1 hook across 1 event