MoonshotAI / MoonshotAI/kimi-code
After update to 0.22.3, `kimi` shows raw ANSI escape codes instead of the TUI on Windows
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.5k
- Forks
- 1.2k
- Avg merge
- 11h 53m
- Merged PRs (30d)
- 350
Description
After updating to 0.22.3, running plain kimi just spits out a wall of raw escape sequences. The TUI never actually renders.
Right at startup I see stuff like:
[2K[38;2;79;168;255m...[39m[38;2;136;136;136mWelcome to Kimi Code!...
and it just stays like that.
What still works:
kimi -p "hello"(non-interactive mode) produces normal readable output.
What doesn't work:
- Running plain
kimiin interactive mode.
Reproduces in:
- Windows Terminal
- Warp
Environment:
- kimi 0.22.3
- Windows (PowerShell 7.5.5)
- No mcp.json configured
kimi doctorpasses clean- Default model is kimi-code/kimi-for-coding
This only started after the update. Interactive mode is basically unusable right now.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing plain kimi in Windows Terminal or Warp and compare it with kimi -p "hello", confirming that only interactive mode emits raw ANSI sequences. Trace the interactive CLI startup and terminal rendering path; done means the TUI renders normally on Windows while non-interactive output remains readable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, typescript
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100