Playbooks · Coding
Kimi Code 2.5.3: steer a running session
Written November 11, 2026
Kimi Code 2.5.3 adds steering: interrupt the model's current request and keep going in the same turn, instead of stopping the session and starting over.
The problem
A Kimi Code session mid-run is hard to redirect. The model is working through a turn, and the only way to change direction is to stop it and start again, losing the flow of the turn. On Windows there was a second problem: MCP servers configured with script commands, such as npx, would not start at all.
What steering does
The 2.5.3 release makes steering interrupt the active model request and continue in the same turn. Send a message while the model is working, and the model picks up the new direction without the turn ending first. The same change adds POST /api/v1/sessions/{session_id}/steer, an endpoint for steering a session with a single request message, for tools that drive Kimi Code over its API rather than through the terminal.
Steering changes what the model does next. It does not rewrite what the session already did, and the release notes say nothing about how the model weighs a steered message against the work already in progress. Treat it as a redirect, not a rewind.
The Windows MCP fix
The same release fixes stdio MCP servers configured with script commands failing to start on Windows. A server started with a command such as npx now starts as expected. If you use script-based MCP servers on Windows, this is the fix that makes them usable again.
Desktop 1.3.3, the same day
Kimi Code Desktop 1.3.3, dated November 10, 2026, lands alongside the CLI release. It improves the steer interruption logic, fixes idle sessions showing "Requesting" instead of streaming new replies, and fixes the same npx MCP server startup failure on Windows.
Keep the two version lines straight. 2.5.x is the CLI, and 1.3.x is the Desktop app. A 2.5.3 change is not a Desktop change, and a 1.3.3 fix is not a CLI fix, even when the two releases land on the same day and fix the same bug.
How to use it
Update the CLI, then send a message while a session is running to steer it. If you drive sessions over the API, use the steer endpoint with the session id. On Windows, check again any script-based MCP server that failed to start before, and confirm it now starts. Install or update with the official script from the Kimi Code repository: curl -fsSL https://code.kimi.com/kimi-code/install.sh | bash on macOS or Linux, or the PowerShell installer on Windows.
Limits
- Steering is new in 2.5.3. The release notes describe the mechanism, not how well it works in practice, and nothing on this page comes from steering a real session.
- The CLI and the Desktop app have separate version lines. Check the number against the product you use.
- Steering interrupts the current request. It does not undo completed tool calls or edits.
Related playbooks
- Kimi Code 2.6.0 canary: read the label
- Open an untrusted repo without running code
- Kimi K3.1 Pro weights are out: what 1.56 TB buys
- Run Kimi, GLM and DeepSeek in the harness you have
Sources
- Release @moonshot-ai/kimi-code@2.5.3 — MoonshotAI/kimi-code, GitHub
- Changelog — Kimi Code Docs
- MoonshotAI/kimi-code — GitHub
Back to: Coding playbooks hub · Also: Kimi K3.1 Pro weights are out: what 1.56 TB buys · Kimi Hosted Agents: a managed harness in the cloud · Addy Osmani's 25 agent skills for coding agents