Key findings
- Moonshot documents a rolling 5-hour window and a monthly total shared with Kimi chat, with no weekly limit on new plans, and one quota across every device and API key.
- Usage limits are raised as a problem in 5 accounts and discussed in 6 more. Practitioners describe a whole window used by one K3 task and a quota gone after 12 minutes of thinking.
- Of the 7 accounts that weigh a plan's value, 5 find the quota too tight against Claude or ChatGPT plans and 2 find it good value.
- Measured windows vary with the task and cache hits: one practitioner put a legacy-plan window at about $7.20 at API prices, while one long K3 task used almost a whole window on the $19 plan (Kimi's plan page shows $ without naming a currency).
Measure Kimi Code's 5-hour window on your own tasks before choosing a plan, because public accounts range from one K3 task using a whole window to a legacy-plan window measured at about 4.5% of the monthly quota. Of the 27 accounts GILD read, published from May 19 to October 28, 2026, the quota is the most discussed concern, and practitioners split on whether a plan is good value.
What Moonshot documents
Kimi Code comes with a Kimi subscription from Plus at $19 a month (Kimi's plan page shows $ without naming a currency) and shares the plan's quota with Kimi chat. New plans keep a rolling 5-hour rate window and a monthly total and drop the weekly limit, while legacy plans keep a 7-day refresh.
When the quota runs out, Extra Usage continues the session, charged by actual usage from an RMB balance at rates close to Kimi Open Platform API pricing, with an optional monthly spending cap. K3.1 Pro Highspeed uses about twice the quota of K3.1 Pro, and K3 with 1M context about twice that of k3-256k.
What practitioners measured
A practitioner on the legacy Allegretto plan measured one 5-hour window at about 4.5% of the monthly quota, worth about $7.20 at API prices.
Others ran out quickly: one K3 task used almost a whole window on the $19 plan (Kimi's plan page shows $ without naming a currency) where a US$20 OpenAI plan finished it in minutes, and another user's quota ended after 12 minutes of thinking on a repository report.
What to test in a pilot
Run each developer's real tasks for a week on one plan with Extra Usage off, record windows used per task, and note which tasks ran on K3.1 Pro, Highspeed, or K3 with 1M context. Then pick plans and set the Extra Usage cap from that record.
- Give each developer their own account, since devices and API keys share one quota.
- Start new sessions after switching models to keep cache hits.
- Set the monthly Extra Usage cap before enabling it.
Methodology
GILD read Moonshot AI's English Kimi Code pages on October 28, 2026 and 42 public accounts from Hacker News, GitHub, Reddit, and X published from May 19 to October 29, 2026, each linked and dated in the Kimi Code Signals. Counts come from those records; measured figures are the practitioners' own and were not rerun by GILD.
Products in this piece
Sources
- Official documentation
- 4
- Public source
- 5
- Kimi Code plans and pricing
- Kimi Code docs: Membership Benefits (quota and Extra Usage)
- Kimi Code docs: Model Configuration
- Kimi Code docs: Overview
- 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)
- r/kimi: I just measured Kimi Quota for Coding on Allegretto (Sep 26, 2026)
- Hacker News comment by KronisLV on 96% to 99% cache rates across harnesses (Jul 22, 2026)