Kimi Code CLI just shipped version 0.29.1, a focused update that quietly introduces one of the more interesting ideas in agentic coding tools: the ability to route different subagents to different models. Alongside that, it adds environment-variable-based configuration for web search and fetch, global MCP timeout controls, and a bug fix that matters a lot if you're running vLLM locally.
The subagent model routing story
Kimi Code already supports a multi-agent architecture where a main orchestrator spawns specialized subagents -- a coder for writing and editing files, an explore agent for read-only codebase search, and a plan agent for architecture work.
These subagents handle focused, parallel work and run in isolated contexts, keeping the main conversation clean.
The new feature in 0.29.1 is experimental secondary-model bindings. It lets you configure a separate model specifically for subagents, rather than having every agent in the hierarchy share the same model. This opens up a cost/quality tradeoff that's genuinely useful in practice:
- Use a powerful, expensive model for the main orchestrator that plans and delegates
- Route subagents to a faster, cheaper model for grunt work like file reads, grep, and code edits
- Override the model on a per-agent-type basis when you want a specific subagent to use something different
Don't miss what's next in AI
Join 300,000+ engineers and researchers who get the signal, not the noise.
- Full access to in-depth AI research breakdowns
- Be the first to know what's trending before it hits mainstream
- Daily curated papers, repos, and industry moves