CLI intermittently freezes with spinning moon; correlated with browser tab state

What version of Kimi Code CLI is running?

0.29.2

Which open platform/subscription were you using?

KIMI Login Subscription

Which model were you using?

KIMI K3 HIGH

What platform is your computer?

Windows 11

What issue are you seeing?

The CLI becomes unresponsive with the "moon" loading animation spinning indefinitely. No output is produced and the agent appears stuck. There are no error messages displayed — the UI simply hangs with the spinning moon.
The issue started suddenly after 4–5 days of normal, uninterrupted usage. Starting a new session works for a few seconds, then freezes again. Network connectivity is confirmed stable.
An unusual correlation I noticed: when a Kimi Chat browser tab is open, the CLI appears to make progress. When the tab is closed, the CLI stops producing output. This has happened consistently across multiple new sessions.

What steps can reproduce the bug?

This bug is intermittent and not reliably reproducible. It occurs during normal CLI usage after the agent begins processing a request. The freeze happens spontaneously — there is no specific sequence of commands or inputs that triggers it predictably.
What I can confirm:

Start kimi in Windows PowerShell.
Send a prompt to the agent.
The moon animation appears and begins spinning.
After a few seconds of normal operation, the CLI freezes with the moon spinning indefinitely.
The freeze persists across new sessions (kimi or kimi --new).

What is the expected behavior?

The CLI should continue processing the agent's response independently of any browser tab state, and should not freeze with the loading animation spinning indefinitely.

Additional information

The CLI is confirmed to be up to date.
The issue is not resolved by restarting the CLI or starting new sessions.
Network connection is normal.
There is no log output or error message shown in the terminal when the freeze occurs.
The correlation with the browser tab being open/closed is consistent but unexplained.

Start by running kimi in Windows PowerShell on version 0.29.2, then compare normal sessions with kimi --new while recording whether a Kimi Chat browser tab is open. The issue is complete when the CLI continues producing the agent response independently of browser-tab state and no longer remains on the spinning moon without output.