kimi-cli tool result 内容丢失 Bug 报告 || kimi-cli tool result Content is missing Bug report

What version of Kimi Code CLI is running?

最新版本

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: kimi-cli MCP tool result 内容丢失
环境：
kimi-cli（最新版）
macOS Darwin 25.2.0
MCP Server 通过 stdio 连接
复现步骤：
配置任意 MCP Server（提供 ReadFile 和 Shell 工具）
让 kimi 模型调用 ReadFile，读取任意文件（如 /tmp/test.txt，内容为 hello world）
观察 tool result
预期结果：
模型收到完整的 tool result，包含文件内容：
{
"content": [{"type": "text", "text": "1\thello world\n"}]
}
实际结果：
模型收到的 tool result 中，元信息正常（如 1 lines read from file starting at line 1），但文件内容为空。模型无法看到文件的实际文本。
Shell 工具同理：cat /tmp/test.txt 返回 Command executed successfully，但 stdout 内容不显示。

What steps can reproduce the bug?

1

What is the expected behavior?

No response

Additional information

No response

---

What version of Kimi Code CLI is running?

latest version

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: kimi-cli MCP tool result content is missing
Environment:
kimi-cli (latest version)
macOS Darwin 25.2.0
MCP Server connects via stdio
Reproduction steps:
Configure any MCP Server (ReadFile and Shell tools provided)
Let the kimi model call ReadFile to read any file (such as /tmp/test.txt, the content is hello world)
Observe tool result
Expected results:
The model receives the complete tool result, including the file contents:
{
"content": [{"type": "text", "text": "1\thello world\n"}]
}
Actual result:
In the tool result received by the model, the meta information is normal (such as 1 lines read from file starting at line 1), but the file content is empty. The model cannot see the actual text of the file.
The same applies to Shell tools: cat /tmp/test.txt returns Command executed successfully, but the stdout content is not displayed.

What steps can reproduce the bug?

1

What is the expected behavior?

No response

Additional information

No response

Reproduce the issue with an MCP server connected via stdio, using the ReadFile and Shell tools described in the report. Trace how their tool results reach the model, checking both file content and command stdout. Done means the model receives the complete content for both tools, not only the metadata or success message.