[Bug] v1.41.0 Windows terminal: `NoneType` crash on path completion + image attachment transmission broken

[weiq0482-dev]

What version of Kimi Code CLI is running?

1.41.0

Which open platform/subscription were you using?

kimi cli

Which model were you using?

kimi2.6

What platform is your computer?

Windows 10

What issue are you seeing?

[Bug] v1.41.0 Windows terminal: NoneType crash on path completion + image attachment transmission broken

Environment

Item	Value
OS	Windows 10/11
Kimi CLI Version	1.41.0
Installation Method	uv tool install kimi-cli
Terminal	Windows PowerShell / Windows Terminal
First Observed	2026-05-03
Last Known Good	2026-05-02 (image attachments worked; no path-completion crashes observed)

Summary

Two distinct bugs have appeared in the v1.41.0 Windows terminal client since approximately 2026-05-02 → 2026-05-03, **
without any client-side upgrade**. This strongly suggests a server-side or client-server protocol change that broke ba
ckward compatibility with the existing v1.41.0 release.

---

Bug 1: NoneType crash during file-path autocompletion

Description

When typing in a git repository directory, the terminal occasionally throws an Unhandled exception during file-pat
h autocompletion. The full stack trace is printed, and the user must press Enter to continue.

Stack Trace

Unhandled exception in event loop: File "...\prompt_toolkit\buffer.py", line 1923, in new_coroutine await coroutine(*a
, **kw) File "...\prompt_toolkit\buffer.py", line 1740, in async_completer async for completion in async_generator: ..
. File "...\kimi_cli\ui\shell\prompt.py", line 723, in _get_deep_paths paths = list_files_git(self._root, scope) File
"...\kimi_cli\utils\file_filter.py", line 247, in list_files_git paths = _parse_ls_files_output(result.stdout) File ".
..\kimi_cli\utils\file_filter.py", line 158, in _parse_ls_files_output for entry in stdout.split("\0"): Exception: 'No
neType' object has no attribute 'split' Press ENTER to continue...

Root Cause

_parse_ls_files_output() receives stdout from a git ls-files subprocess. When the subprocess fails or returns N one, the code calls .split() on None without a guard, causing the AttributeError.

Suggested Fix

def _parse_ls_files_output(stdout: str | None) -> list[str]:
    if stdout is None:
        return []
    return [entry for entry in stdout.split("\0") if entry]
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Bug 2: Image attachment transmission broken in terminal client
Description
Images that are pasted or referenced in the Kimi CLI terminal session (e.g., via @N local-file references or clipboard
paste) are no longer visible to the AI assistant. This feature was working correctly on 2026-05-02.
Verified Checks
• [x] New PowerShell session does not resolve the issue
• [x] Plain-text messages continue to work normally
• [x] Only image attachments are affected
• [x] Client version remained at 1.41.0 (no local upgrade performed)
• [x] Local screenshot tool (clipmon) is functioning correctly; files exist on disk
Reproduction Steps
1. Open Kimi CLI v1.41.0 in Windows PowerShell.
2. Take a screenshot (or use an existing @N reference).
3. Attempt to send the image to the AI assistant (paste, or type @N).
4. The AI assistant reports it cannot see the image.
Expected Behavior
Image attachments should be transmitted to the AI assistant exactly as they were on 2026-05-02.
Actual Behavior
The AI assistant receives no image data; the attachment appears to be dropped silently by the client-server pipeline.
Suspected Cause
A server-side update (client-keepalive, protocol revision, or attachment-gateway change) broke compatibility with the
v1.41.0 terminal client's image-transmission path.
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Common Pattern
Both bugs share the same timeline and context:
 Factor            Bug 1 (crash)                   Bug 2 (image TX)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 Client version    1.41.0 (unchanged)              1.41.0 (unchanged)
 First observed    2026-05-03                      2026-05-03
 Last known good   Not explicitly tracked          2026-05-02
 Platform          Windows Terminal / PowerShell   Windows Terminal / PowerShell
 Workaround        Local source patch              AI reads local files directly via filesystem
Because the client was not upgraded and two unrelated subsystems (path-completion subprocess handling + image attachme
nt transmission) broke simultaneously, the most plausible explanation is a server-side deployment that introduced inco
mpatible expectations or changed the wire protocol.
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Impact
• Bug 1 Severity: Medium — does not corrupt data, but disrupts interactive workflow with a full stack trace dump.
• Bug 2 Severity: High — breaks core multimodal functionality in the terminal client; users cannot share screenshots o
  visual context with the AI.
• Combined Workaround: Press Enter to dismiss the crash; for images, manually specify the local @N tag so the AI can r
  d the file directly from disk.
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Attachments
• Screenshot of Bug 1 stack trace: @135 (see local file 20260503_085328_037.png)
• Screenshot of Bug 2 symptom (AI unable to see image): @138, @139 (see local files)
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Request
1. Please confirm whether a server-side or client-keepalive update was deployed between 2026-05-02 and 2026-05-03.
2. If so, please advise whether a hotfix or v1.41.1 patch release is planned.
3. If terminal image transmission is deprecated, please document the recommended alternative workflow.

### What steps can reproduce the bug?

Bug 1 的复现步骤（NoneType 崩溃）：
### Steps to Reproduce

1. Ensure Kimi CLI v1.41.0 is installed via `uv tool install kimi-cli` on Windows.
2. Open a new Windows PowerShell window.
3. `cd` into any git repository directory.
4. Launch Kimi CLI: `kimi`
5. Start typing a message that triggers file-path autocompletion (e.g., type `/` or a few characters that match existi
ng file names).
6. Observe the terminal: an `Unhandled exception` stack trace appears, ending with `Exception: 'NoneType' object has n
o attribute 'split'`.
7. Press `Enter` to dismiss the exception; the session resumes but autocompletion is broken for that keystroke.
  Bug 2 的复现步骤（图片传输失效）：
### Steps to Reproduce

1. Ensure Kimi CLI v1.41.0 is installed via `uv tool install kimi-cli` on Windows.
2. Open a new Windows PowerShell window (to rule out session state issues).
3. Launch Kimi CLI: `kimi`
4. Take a screenshot using any tool (e.g., `Win+Shift+S`), or reference an existing local image via the `@N` syntax (e
.g., `@135`).
5. Paste the image into the terminal session, or type the `@N` reference in the chat input.
6. Send the message.
7. Observe the AI assistant's response: it reports that no image was received or that it cannot see the image content.
8. Repeat steps 4-7 with a brand-new PowerShell session — the issue persists.

### What is the expected behavior?

_No response_

### Additional information

<img width="1109" height="932" alt="Image" src="https://github.com/user-attachments/assets/99186358-2734-40b7-8246-0c8d61810b1c" />
<img width="1106" height="920" alt="Image" src="https://github.com/user-attachments/assets/2978a7ae-36c0-4bf5-b108-f966579c6cce" />