@__oQuery: Everyone says K3 is easy to use, so I opened one and tried the latest Kimi Code. But I found that Kimi's development team might really not have a good feel for design. As soon as I started using it, I noticed many frustrating issues: 1. The ask user question in figure one…

X AI KOLs Following News

Summary

User posts criticism of Kimi Code's interaction design, pointing out issues such as the unreasonable submission method of the ask user question tool and the state bar shaking due to container height changes during command selection, hoping the Kimi team will optimize.

Everyone says K3 is easy to use, so I opened one and tried the latest Kimi Code. But I found that Kimi's development team might really not have a good feel for design. As soon as I started using it, I noticed many frustrating issues: 1. The ask user question tool in Figure 1: At first, I didn't know how to submit because pressing Enter triggered a deselect operation. After looking several times, I realized that submit was actually an interaction in the same column as the Tab key. This is clearly unreasonable. 2. The select after entering command interaction in Figure 2: When selecting up and down, the height of the scroll container changes, causing the status bar at the bottom to jump up and down. I don't know what purpose it serves. This is clearly CLS. Hope the Kimi team can optimize this.
Original Article
View Cached Full Text

Cached at: 07/17/26, 12:19 AM

People are saying that K3 is great to use, so I tried the latest Kimi Code. But I found that the Kimi development team might not really have a good sense for design. Right from the start, I noticed several frustrating issues:

  1. The “ask user question tool” in Figure 1: I had no idea how to submit at first, because pressing Enter triggers a reverse selection. I only realized after a few looks that submitting requires pressing Tab – an interaction that is placed in the same column as the Tab key. This is clearly unreasonable.

  2. The selection in Figure 2 after entering command mode: when scrolling up and down, the height of the scroll container changes, causing the status bar at the bottom to jump up and down constantly. I don’t understand what purpose it serves. This is clearly CLS.

I hope the Kimi team can optimize this.

Similar Articles

Kimi K2.7 Code feels more useful than flashy

Reddit r/AI_Agents

Kimi released K2.7 Code, a coding-focused AI model with improved benchmarks and 30% lower thinking token usage, emphasizing practical performance in long coding loops and agent tool integration rather than flashy scores.

@berryxia: Looks like Kimi has been quietly making big moves. After watching these demo videos, my back didn't get cold — instead, I got pumped and felt truly impressed! Kimi today directly upgraded AI agents from "just chatting" to "operating browsers like humans." They released the Web Bridge browser extension.

X AI KOLs Timeline

Kimi has released the Web Bridge browser extension, enabling AI agents to operate browsers like humans, performing tasks such as searching, scrolling, and clicking, while supporting multiple AI tools.