Will it last?
This page is a projection of the one entry record, the Transparency factor that Support covers. The full verdict is set by all four factors together, floor-weighted so the weakest caps the whole.
- AssessUse & modify + Transparency
- ImplementData control + Doesn't fail you
- UseDoesn't fail you
- SupportTransparency
Common problems & fixes
Aggregated common pitfalls (not an exhaustive catalogue):
- Out-of-memory / sharding failures. The 1T model must be sharded across a multi-GPU/multi-node cluster; size tensor/pipeline parallelism to your hardware, or use KTransformers CPU-offload.
- Block-FP8 kernel or engine errors. Match your vLLM/SGLang/TensorRT-LLM version to one that supports the block-FP8 weights and MLA attention; version mismatches are a common cause.
- Garbled or over-verbose Instruct output. You are almost certainly not applying the chat
template - use
apply_chat_template, and don't prompt the Base checkpoint as a chat model. - Non-reproducible results / silent updates. You floated on
main; pin an exact revision and verify checksums.
Versions, changelog & cadence
Kimi K2 ships as Base and Instruct checkpoints on the verified moonshotai org, tracked
as immutable Hugging Face revisions - the revision hash is your changelog anchor: pin it, and
diff against a newer revision when you choose to upgrade. Moonshot's "Kimi K2: Open Agentic
Intelligence" technical report accompanies the release and documents what the model is. (Any newer
Kimi variants beyond K2 are out of scope for this entry until independently verified.)
Community & support channels
- Hugging Face model discussion tabs on the
moonshotaiorg (ev-kimi-hf) for usage questions. - GitHub issues on
moonshotai/Kimi-K2(ev-github) for deployment, serving-engine, and reproduction problems.
There is no paid support tier for the open weights - this is community and maintainer support around an open-weight release.
Tracked known issues
Drawn from model-card and third-party caveats rather than a formal issue tracker (hence partial):
- China-aligned topic censorship on politically sensitive prompts.
- Lighter safety coverage than frontier labs, with no companion guard model.
- Operational burden of a 1T-parameter model - multi-node infrastructure is required with no small fallback variant.
How this scores
The ownership factor this domain covers, drawn from the one entry record.
TransparencyDo you know what it is: weights, training, behaviour, and legible terms?
WeakYou cannot see what the model is: the technical report documents a 1T/32B MoE trained on 15.5T tokens with MuonClip, but the training corpus and training code are closed, and the weights carry China-aligned topic censorship you cannot inspect.
Sources
The same evidence records as the entry sheet. Read means the text was verified; unverified means it is known to exist but not yet read.