Capability change announced Aug 13, 2026
Kimi For Coding (kimi.com) documents a capability change: “0.36.0 (2026-08-13) Features Upgrade the experimental subagent model setting to a model pool: the [secondary_model] section can now hold a set of…”
- Hosting route
- First-party API
- Affected scope
- Not stated in the notice
- Announced
- Aug 13, 2026
- First seen by ModelClock
- Oct 5, 2026
What the provider published
kimi.com ↗0.36.0 (2026-08-13)
Features
Upgrade the experimental subagent model setting to a model pool: the
[secondary_model]section can now hold a set of candidate models with descriptions, and the main agent picks from them per spawn based on the task. SetKIMI_CODE_EXPERIMENTAL_SECONDARY_MODEL=1(or the master flagKIMI_CODE_EXPERIMENTAL_FLAG=1) before starting Kimi to enable it. Recommended setups:Minimal: run
/secondary-modelin the TUI, or write a singledefault_modelline inconfig.toml, to make every subagent run the same model by default; addforce = trueto pin that choice so the main agent cannot override it.Declare a named pool with a one-line scenario description for each alias — the descriptions are what the main agent sees when choosing: toml
[ secondary_model ] default_model = "kimi-code/kimi-for-coding-highspeed" [ secondary_model . models ] "kimi-code/kimi-for-coding-highspeed" = "Fast and cheap — good for daily refactoring, code explanation, and small edits." "kimi-code/k3" = "Strong at complex reasoning and deep debugging — pick it for hard problems."
Read from the provider's text; the quote is the provider's exact lines.