窗口切换，导致焦点事件信息打印在kimi cli输入中 || Window switching causes focus event information to be printed in the kimi cli input
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Reproduce on Ubuntu 24.04 with i3wm, Terminator, and TERM=xterm-256color by switching windows while kimi is running. Start by locating the CLI's terminal input and focus-event handling; done means the \e[I and \e[O sequences are consumed or disabled and [I/[O no longer appear in the input area.
Written by the indexing model from the issue text.
Description
What version of Kimi Code CLI is running?
1.39.0
Which open platform/subscription were you using?
/setup
Which model were you using?
kimi-for-coding
What platform is your computer?
No response
What issue are you seeing?
▌ 环境: Ubuntu 24.04, i3wm, $TERM=xterm-256color
▌ 现象: 每次 i3 窗口切换，kimi 终端输入区会出现 [O 和 [I 字符
▌ 原因: xterm 焦点事件序列 \e[I / \e[O 未被正确处理
▌ 复现: 任何 xterm-compatible 终端 + i3 下 100% 复现
▌ 期望: kimi-cli 应像 vim/tmux 一样正确消费或禁用焦点事件序列
What steps can reproduce the bug?
启动kimi后，使用相同终端（terminator）+ i3wm，只要切换窗口就会出现
What is the expected behavior?
No response
Additional information
No response
What version of Kimi Code CLI is running?
1.39.0
Which open platform/subscription were you using?
/setup
Which model were you using?
kimi-for-coding
What platform is your computer?
No response
What issue are you seeing?
▌ Environment: Ubuntu 24.04, i3wm, $TERM=xterm-256color
▌ Phenomenon: Every time the i3 window is switched, [O and [I characters will appear in the kimi terminal input area
▌ Reason: xterm focus event sequence \e[I / \e[O is not handled correctly
▌ Reproduction: 100% reproduction under any xterm-compatible terminal + i3
▌ Expectation: kimi-cli should correctly consume or disable focus event sequences like vim/tmux
What steps can reproduce the bug?
After starting kimi, use the same terminal (terminator) + i3wm, it will appear as long as you switch the window
What is the expected behavior?
No response
Additional information
No response
- Dominant language
- Python
- Stars
- 11.4k
- Forks
- 1.3k
- Avg merge
- 9h 47m
- Merged PRs (30d)
- 2
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.
More from MoonshotAI/kimi-cli
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MoonshotAI/kimi-cli#2629 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
MoonshotAI/kimi-cli#2624 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MoonshotAI/kimi-cli#2576 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
MoonshotAI/kimi-cli#2564 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MoonshotAI/kimi-cli#2532 ·
All issues in MoonshotAI/kimi-cli
Similar issues
-
area/auth bug comp/agent P3 platform/discord type/security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#117848 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100