Kimi CLI Bug Report — Double Enter Key & `/sessions` Feedback Loss

What version of Kimi Code CLI is running?

0.20.0

Which open platform/subscription were you using?

Ubuntu 24.04.4 LTS

Which model were you using?

kimi-cli

What platform is your computer?

Linux 6.8.0-124-generic x86_64 x86_64

What issue are you seeing?

Environment

• Kimi CLI version: 0.20.0 (reported as latest by updater, published 2026-06-25)
• Installation path: /home/iqr8/.kimi-code/bin/kimi
• OS: Linux
• Terminal: Alacritty 0.13.2
• Config migrated: 2026-06-15 from ~/.kimi to ~/.kimi-code, no migration errors

---

Issue 1: Enter Key Is Registered Twice Inside Kimi

Summary

Inside the Kimi CLI chat prompt, pressing Enter once appears to be processed twice (e.g., message submits twice or a single Enter causes two submissions).

Validation

I wrote a raw terminal key-capture script (validate-enter-key.js) and ran it in the same terminal. It confirmed that Alacritty emits exactly one Enter event per physical key press at the OS/terminal level.

Example output:

[1782469490406] Enter detected
[1782469490670] Enter detected
[1782469490972] Enter detected

Timestamps match single human key presses — no duplicates within 50 ms.

Expected Behavior

One physical Enter press = one submit/newline action.

Actual Behavior

One physical Enter press = two actions (appears duplicated).

---

Issue 2: /sessions "Reject and Provide Feedback" Loses Feedback

Summary

When using /sessions, the UI appears to auto-select the first session. Choosing "Reject and provide feedback" immediately rejects the session as if no feedback was entered.

Likely Root Cause

This is probably the same bug as Issue 1. After selecting "Reject and provide feedback", the UI opens a feedback input prompt. The duplicated Enter event submits the empty feedback field before the user can type.

Expected Behavior

Selecting "Reject and provide feedback" should wait for the user to type feedback and then submit it.

Actual Behavior

The session is rejected immediately with no feedback.

---

Steps to Reproduce

Issue 1

1. Open Kimi CLI in Alacritty.
2. Type any message.
3. Press Enter once.
4. Observe that the message appears to be submitted/processed twice.

Issue 2

1. Open Kimi CLI in Alacritty.
2. Run /sessions.
3. Select any session.
4. Choose "Reject and provide feedback".
5. Observe that the rejection happens instantly without allowing feedback input.

---

Workaround

Use Kitty (or another terminal) instead of Alacritty. The user confirmed the raw key events are correct in Alacritty, so the duplication appears to be specific to how Kimi 0.20.0 handles input from Alacritty.

---

Additional Notes

• TERM inside the tool subprocess was reported as dumb, but the user confirmed the issue only happens inside Kimi.
• No custom input hooks or skills are configured in ~/.kimi-code/config.toml or the project .kimi/ directory.
• Migration from legacy ~/.kimi completed without errors.

---

Attachments

• validate-enter-key.js — raw terminal key-capture script used for validation.

What steps can reproduce the bug?

Run kimi cli in Alacritty terminal in wayland ubuntu

What is the expected behavior?

No response

Additional information

No response

Start with the attached validate-enter-key.js result, then reproduce the chat prompt and /sessions flow in Alacritty and Kitty. Trace the input handling from one Enter event into submission and the “Reject and provide feedback” prompt. Done means one physical Enter causes one action and feedback is not submitted before it is entered.