#kimi code setup
1 messages · Page 1 of 1 (latest)
@stoic orchid pls help
@stoic orchid
Yep — that’s expected.
kimi-coding and moonshot are two different providers in OpenClaw:
- Kimi Code subscription →
kimi-coding/...(coding-focused) - Moonshot Kimi (non-coding/general K2.5) →
moonshot/...
Their keys/endpoints are separate, so a Kimi Code key won’t automatically unlock Moonshot models.
If you want the non-coding Kimi model:
- Add Moonshot auth
openclaw onboard --auth-choice moonshot-api-key - Switch model
/model moonshot/kimi-k2.5
(or CLI:openclaw models set moonshot/kimi-k2.5) - Verify
openclaw models status
For “which is better for OpenClaw?”:
- General assistant / mixed tool use: usually
moonshot/kimi-k2.5 - Code-heavy tasks:
kimi-coding/k2p5
Docs:
- https://docs.openclaw.ai/providers/moonshot
- https://docs.openclaw.ai/concepts/models
- live community model picks: #models (these change fast)
AM I ABLE TO USE MOONSHOT/KIMI-K-2.5 IF I AM ONLY ON THE KIMI CODE SUBSCRPTION (MODERATO) PLAN?