GILD verdict
Adopt Kimi Code when developers want Kimi K3.1 Pro in a coding agent at a monthly plan price, or a second model for review.
Measure the 5-hour window on real tasks first, cap Extra Usage, and keep approvals on for file changes and shell commands.
Kimi Code
AI Coding Agent by Moonshot AI
−36 NegativeFit and limits
Who it fits
- Developers want Kimi K3.1 Pro, with its 1M-token context window, in a terminal, VS Code, the desktop, or Zed and JetBrains over ACP.
- A plan price per developer matters more than the largest allowance, and sessions are short enough to fit the 5-hour window.
- You want a second model beside Claude or GPT for adversarial review, or Kimi models inside Claude Code or OpenCode through the plan's API key.
- The work suits skills, MCP servers, plugins, and hooks, which Kimi Code supports in the CLI.
Where it falls short
- Practitioners report one long K3 task using most of a 5-hour window on the $19 plan (Kimi's plan page shows $ without naming a currency), a quota gone after 12 minutes of thinking, and half a weekly allowance used in a day and a half by a user who renewed an Anthropic plan as well.
- Multi-step tasks can stall: one user on K3 with high thinking effort reports tasks frozen for tens of minutes to hours, with time to first token up to 243 seconds and silent 429 retries.
- A user reported in July 2026 that Kimi Code ran rm -rf on two template directories without asking. Kimi's docs say file changes and shell commands ask for confirmation by default, so check every permission rule a developer adds.
- Kimi Code's English documentation states no SSO, SCIM, audit log, retention, or training terms, and Extra Usage is not yet available for Enterprise.
Implementation reality
Measure the quota before choosing plans
Run a week of each developer's real tasks on Plus or Pro with Extra Usage off, and record windows used per task with /usage. One practitioner measured a legacy Allegretto window at about 4.5% of the monthly quota and about $7.20 at API prices.
Cap Extra Usage before turning it on
Extra Usage continues every session past the quota and is charged by actual usage from an RMB balance. Set the monthly spending cap in the Extra Usage settings first; without it there is no cap.
Keep approvals on
Leave file changes and shell commands on confirmation, add permission rules only for tools you have reviewed, and avoid wildcard rules that allow every MCP tool. Ask When Needed mode approves MCP tool calls automatically.
Pick models and editors per task
K3.1 Pro runs in thinking mode only, its Highspeed version uses about twice the quota, and K3 with a 1M context uses about twice the quota of k3-256k. Start a new session after switching to K3.1 Pro, and connect Zed or JetBrains through kimi acp.
What to verify before you buy
- Kimi Code devices inactive for over 30 days are automatically unbound.
- With annual billing, Kimi Code lists Plus at $15 a month ($180 a year), Pro at $31 a month ($372 a year), Max at $79 a month ($948 a year) and Ultra at $159 a month ($1,908 a year).
What to measure in your pilot
- Record quota used per task for the first month; move a developer to a larger plan or another agent if they hit the 5-hour window more than twice a week.
- Track Moonshot's English terms for retention, training, and SSO; hold company code back until they are published or signed.
- Retest after each Kimi Code CLI minor release for the stalls and approval behavior reported in July and August 2026.
Sources
- Official documentation
- 12
- Public source
- 7
- Kimi Code plans and pricing
- Kimi Code docs: Membership Benefits (quota and Extra Usage)
- Kimi Code docs: Model Configuration
- Kimi Code docs: FAQ (endpoints and billing by platform)
- Kimi Code docs: Overview
- Kimi Code CLI docs: Getting started
- Kimi Code CLI docs: Using Kimi Code CLI in IDEs
- Kimi Code CLI docs: Model Context Protocol
- Kimi Code CLI docs: Data locations
- Kimi Code docs: Use in third-party tools, Claude Code
- MoonshotAI/kimi-code on GitHub (MIT license)
- Hacker News comment by SwellJoe on a 5-hour window used in one K3 task (Jul 18, 2026)
- Hacker News comment by thevinter on a quota exhausted after 12 minutes of thinking (Jul 19, 2026)
- Hacker News comment by ffsm8 on half a weekly allowance used in a day and a half (Jul 22, 2026)
- MoonshotAI/kimi-code issue #2570: multi-step tasks stall for hours with silent 429 retries (Aug 3, 2026)
- MoonshotAI/kimi-code issue #2327: unauthorized deletion of template files by the agent (Jul 28, 2026)
- r/kimi: I just measured Kimi Quota for Coding on Allegretto (Sep 26, 2026)
- Hacker News: Kimi-code not performing well (Jul 30, 2026)
- Kimi Code: plan page