mirror of
https://github.com/openclaw/openclaw.git
synced 2026-08-04 02:51:43 +00:00
99ec30b44b
* feat(plugins): catch code-mode drift between catalogs sharing one model Adds a contract test that groups bundled catalog rows by shared upstream model and requires every row in a group to declare compat.codeMode once any sibling does. Rows sharing a model id group automatically; rows under different ids opt in with the new manifest-only `upstreamModel` marker. Moves the kimi catalog into its manifest so the scan can see it, and records the tier reseller catalogs were silently missing as explicit "capable". * docs: regenerate docs map for the shared-model code-mode section
26 lines
908 B
Markdown
26 lines
908 B
Markdown
# OpenClaw Kimi Coding Provider
|
|
|
|
Official OpenClaw provider plugin for Kimi Coding.
|
|
|
|
Install from OpenClaw:
|
|
|
|
```bash
|
|
openclaw plugins install @openclaw/kimi-provider
|
|
openclaw gateway restart
|
|
```
|
|
|
|
See <https://docs.openclaw.ai/providers/moonshot> for setup and configuration.
|
|
|
|
## Catalog notes
|
|
|
|
Model rows live in `openclaw.plugin.json` under `modelCatalog.providers.kimi`.
|
|
|
|
- `k3` serves up to 1M context, tier-gated server-side; `k3-256k` is the cheaper
|
|
256K variant of the same weights. Both point at `moonshot/kimi-k3` through
|
|
`upstreamModel`, which keeps their `compat` capability tiers aligned with the
|
|
`moonshot` catalog for the same model.
|
|
- Legacy `k3[1m]` was retired upstream and normalizes to `k3` for shipped
|
|
configurations.
|
|
- `KIMI_K3_MODEL_IDS` in `provider-policy-api.ts` must cover exactly the catalog
|
|
rows that carry a K3 `thinkingLevelMap`; `provider-catalog.test.ts` asserts it.
|