MoonshotAI / MoonshotAI/kimi-cli

Web 端历史会话中的图片/文件在重新进入对话后被自动重复发送 || Pictures/files in historical conversations on the Web are automatically sent repeatedly after re-entering the conversation.

Open
#1,945 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
11.4k
Forks
1.3k
Avg merge
9h 47m
Merged PRs (30d)
2

Description

What version of Kimi Code CLI is running?

1.35

Which open platform/subscription were you using?

/login

Which model were you using?

No response

What platform is your computer?

No response

What issue are you seeing?

Bug 标题: Web 端历史会话中的图片/文件在重新进入对话后被自动重复发送
问题描述: 用户在 Kimi Code Web 端进行对话时上传了图片和文件。退出 Web 端后重新进入该对话,当用户仅输入纯文字消息时,系统会自动将之前对话中上传过的所有图片和文件重新发送一遍,导致重复上传。
复现步骤:
1.
在 Kimi Code Web 端开启一个对话
2.
在对话中上传若干图片和/或文件
3.
退出 Kimi Web 端(关闭页面或离开)
4.
重新进入该对话
5.
仅输入文字内容(输入框中未显示任何附件)
6.
发送文字消息
实际结果:

文字消息成功发送

但系统会自动将步骤 2 中上传过的所有历史图片和文件重新发送一遍

聊天界面显示这些历史附件被重复上传
预期结果: 仅发送用户当前输入的文字内容,不应自动携带或重复发送任何历史附件。

What steps can reproduce the bug?

Bug 标题: Web 端历史会话中的图片/文件在重新进入对话后被自动重复发送
问题描述: 用户在 Kimi Code Web 端进行对话时上传了图片和文件。退出 Web 端后重新进入该对话,当用户仅输入纯文字消息时,系统会自动将之前对话中上传过的所有图片和文件重新发送一遍,导致重复上传。
复现步骤:
1.
在 Kimi Code Web 端开启一个对话
2.
在对话中上传若干图片和/或文件
3.
退出 Kimi Web 端(关闭页面或离开)
4.
重新进入该对话
5.
仅输入文字内容(输入框中未显示任何附件)
6.
发送文字消息
实际结果:

文字消息成功发送

但系统会自动将步骤 2 中上传过的所有历史图片和文件重新发送一遍

聊天界面显示这些历史附件被重复上传
预期结果: 仅发送用户当前输入的文字内容,不应自动携带或重复发送任何历史附件。

What is the expected behavior?

No response

Additional information

No response


What version of Kimi Code CLI is running?

1.35

Which open platform/subscription were you using?

/login

Which model were you using?

No response

What platform is your computer?

No response

What issue are you seeing?

Bug title: Images/files in historical sessions on the web are automatically sent repeatedly after re-entering the session
Problem description: Users uploaded images and files during conversations on the Kimi Code web side. After exiting the web client and reentering the conversation, when the user only enters a plain text message, the system will automatically resend all images and files uploaded in the previous conversation, resulting in repeated uploads.
Reproduction steps:
1.
Start a conversation on Kimi Code web
2.
Upload several images and/or files in the conversation
3.
Exit Kimi Web (close the page or leave)
4.
Re-enter the conversation
5.
Only enter text content (no attachments are displayed in the input box)
6.
Send text message
Actual result:

Text message sent successfully

However, the system will automatically resend all historical images and files uploaded in step 2.

The chat interface shows that these historical attachments have been uploaded repeatedly.
Expected results: Only the text content currently entered by the user is sent, and any historical attachments should not be automatically carried or re-sent.

What steps can reproduce the bug?

Bug title: Images/files in historical sessions on the web are automatically sent repeatedly after re-entering the session
Problem description: Users uploaded images and files during conversations on the Kimi Code web side. After exiting the web client and reentering the conversation, when the user only enters a plain text message, the system will automatically resend all images and files uploaded in the previous conversation, resulting in repeated uploads.
Reproduction steps:
1.
Start a conversation on Kimi Code web
2.
Upload several images and/or files in the conversation
3.
Exit Kimi Web (close the page or leave)
4.
Re-enter the conversation
5.
Only enter text content (no attachments are displayed in the input box)
6.
Send text message
Actual result:

Text message sent successfully

However, the system will automatically resend all historical images and files uploaded in step 2.

The chat interface shows that these historical attachments have been uploaded repeatedly.
Expected results: Only the text content currently entered by the user is sent, and any historical attachments should not be automatically carried or re-sent.

What is the expected behavior?

No response

Additional information

No response

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

No files or tests are named. Reproduce the issue through the Web conversation flow by uploading attachments, leaving, re-entering, and sending plain text; trace how historical conversation state is reused when the message is sent. Done means a text-only message after re-entry sends no prior images or files, while current attachments still work.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
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.