What a kimi code plan actually buys: Moonshot AI's coding agent on desktop, terminal and IDE under one membership, plus the K3 tier condition nobody mentions.
Read the full page: https://kimi-code-plan.github.io/
Buy into this if you want one subscription that follows you from a desktop app to a terminal to an IDE plugin, and if a very large context window is the thing your current assistant keeps failing on, since the product banner puts K3 at up to one million context tokens. It is the wrong purchase if you need a published rate card before committing, because the membership pricing page did not load when this review was compiled, and the plan names sit behind it. The other caveat is that K3 is gated, described as available on certain plans and above rather than on everything. If your actual goal is one site or app rather than an agent in your repo, Begin.sh hands you the files instead.
- What a kimi code plan actually includes — Kimi Code is Moonshot AI's coding agent, and the product page is unusually direct about the shape of the offer: one subscription, code anywhere. The same plan c
- The K3 condition — A banner across the product page announces that K3 is available and supports up to one million context tokens. Directly under the plan section sits a single lin
- Why the prices are not on this page — Moonshot publishes membership pricing at a dedicated page, and that page returned nothing when it was fetched for this review, so no figure appears here. That i
- Where the real documentation lives — Three places, all reachable from the product page. The English documentation sits under the Kimi Code docs path and is the only source that will tell you curren
- When you do not need a coding plan at all — Plenty of work that feels like development is really a one-off artefact: a landing page, a small marketing site, a clone of a layout you like, a simple app to h
Open Begin.sh: begin.sh
This is an independent page written by a third party; it is not operated by or affiliated with Moonshot AI or Kimi, and all trademarks belong to their respective owners.
Last reviewed: 2026-09-22