Kimi Code CLI repeatedly hangs or returns no final response on Windows

What version of Kimi Code is running?

0.31.0

Which open platform/subscription were you using?

Windows 10, build 10.0.26200.8875, x64, Windows Terminal / PowerShell

Which model were you using?

kimi-k2.6, kimi-k2.7-code, and kimi-k3 High Thinking

What platform is your computer?

Windows 10, build 10.0.26200.8875, x64, Windows Terminal / PowerShell

What issue are you seeing?

Kimi Code CLI repeatedly stops without returning a final response on Windows.

Environment:

• Windows 10, build 10.0.26200.8875
• Kimi Code CLI 0.31.0
• PowerShell / Windows Terminal
• Paid account with available balance

Affected models:

• Kimi K2.7 Code
• Kimi K3 with High thinking
• Kimi K2.6 with thinking enabled

Observed behaviour:

1. I start a new Kimi CLI session.
2. I send either a coding task or even a very simple message.
3. Kimi sometimes completes tool calls but never produces the final response.
4. The input field becomes available again or the interface remains stuck, with no error shown.
5. Esc, Ctrl+C and Ctrl+S often do not recover the session.
6. The same problem occurs in a fresh session with 0% context and no project involved.

Most recent session:
session_f2e9388-16c1-412b-ae30-dd5106571ff3

Expected behaviour:
Kimi should return a response or display a clear network/API/error message instead of silently stopping or hanging.

This is reproducible across multiple sessions and models. Please check the session/server logs and advise whether this is a known Windows CLI streaming issue.

What steps can reproduce the bug?

1. Open Windows Terminal or PowerShell.
2. Start Kimi Code CLI by running kimi.
3. Start a fresh session with 0% context.
4. Select kimi-k2.6 with Thinking enabled, kimi-k2.7-code, or kimi-k3 with High Thinking.
5. Send a simple message such as “Who are you?” or ask it to perform a coding task.
6. Kimi sometimes completes its tool calls but does not produce a final response. In other cases, even a simple message receives no response.
7. The input field either becomes available again without an answer or the CLI remains stuck indefinitely.
8. Esc, Ctrl+C, and Ctrl+S frequently do not recover the session, so the terminal has to be closed.

The issue has occurred repeatedly in project directories and in a completely fresh session launched from C:\WINDOWS\system32, so it does not appear to be caused by a specific repository.

Most recent affected session:
session_f2e9388-16c1-412b-ae30-dd5106571ff3

Context usage in that session was 0%.

What is the expected behavior?

Kimi should return a normal final response after completing its reasoning or tool calls.

If the request fails because of overload, billing, authentication, networking, or another server-side problem, the CLI should display a clear error message and allow the user to retry. It should not silently return to the input field or remain stuck indefinitely.

Additional information

This has happened across multiple sessions and models:

• kimi-k2.6 with Thinking enabled
• kimi-k2.7-code
• kimi-k3 with High Thinking

The account is paid and has available balance. Kimi sometimes performs the requested coding changes successfully but hangs before giving the final summary.

Kimi Code CLI version: 0.31.0
Operating system: Windows 10 build 10.0.26200.8875, x64
Terminal: Windows Terminal / PowerShell

Please inspect the server and streaming logs for the supplied session ID. Screenshots are attached.

Start by reproducing the hang with the kimi entry point in Windows Terminal or PowerShell, using the listed models and the supplied session ID. Inspect the server and streaming logs for session_f2e9388-16c1-412b-ae30-dd5106571ff3, then trace the Windows CLI path involved. Done means the CLI returns a final response or displays a clear error and permits retrying.