MoonshotAI / MoonshotAI/kimi-code

Windows TUI prints raw ANSI escape sequences instead of rendering (Windows Terminal, PowerShell, cmd)

Open
#1,792 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
7.5k
Forks
1.2k
Avg merge
11h 53m
Merged PRs (30d)
350

Description

Version

Kimi Code CLI 0.26.0

Platform
  • Windows 11
  • Reproduced in:
    • Windows Terminal + PowerShell 7
    • Windows Terminal + cmd
    • Warp + PowerShell 7
  • Install path: %USERPROFILE%\.kimi-code\bin\kimi.exe
What happens

Running kimi dumps the whole TUI as literal escape text. Colors, box drawing, cursor control, etc. never render. The UI is unusable.

You get stuff like:

←[?2026h ←[0m←]8;;←[?2026l←[?25l←[?2004h←[>7u←[?u
←[2K ←[38;2;79;168;255m╭────...
←[2K ←[38;2;79;168;255m│←[39m  Welcome to Kimi Code!
...
←[38;2;224;224;224mK2.7 Coding thinking←[39m

So sequences are being written, but nothing is interpreting them. The ←[ form is the usual Windows "ESC shown as text" look.

Expected

Normal interactive TUI: welcome panel, prompt, colors, no visible escape codes.

Steps
  1. Install Kimi Code CLI 0.26.0 on Windows.
  2. Open Windows Terminal.
  3. Run in PowerShell: kimi
  4. Same with cmd.exe: kimi
  5. Observe raw escape sequences instead of a rendered UI.
What I already tried
  • Confirmed it is not Warp-only. Same failure in Windows Terminal with PowerShell and cmd.
  • Set HKCU\Console\VirtualTerminalLevel = 1
  • Set user env COLORTERM=truecolor and FORCE_COLOR=3
  • Forced VT processing on the console handle before launch
  • None of that fixed it
Notes
  • Looks like a Windows console / VT handling problem in the 0.26.0 TUI path, not a single terminal emulator bug.
  • Visible control sequences include truecolor SGR, synchronized output (?2026h), OSC 8 hyperlinks, and Kitty keyboard protocol bits (>7u, ?u).
  • Non-TUI paths are fine as a workaround (kimi web, kimi -p "...").
Screenshot
Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the 0.26.0 TUI path with kimi in Windows Terminal using both PowerShell and cmd, then inspect the Windows console and terminal-output initialization. Compare behavior with the non-TUI commands and verify that the interactive UI renders colors, box drawing, cursor control, and hyperlinks without visible escape sequences.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.