What version of Kimi Code CLI is running?
moonshot-ai.kimi-code@0.5.10
Which open platform/subscription were you using?
Kimi Coding Plan
Which model were you using?
kimi-for-coding
What platform is your computer?
Darwin 23.0.0 arm64 arm
What issue are you seeing?
Bug description
In Plan mode, when Kimi writes a plan file (e.g. ~/.kimi/plans/<name>.md), the VS Code extension chat webview renders the absolute path as plain text in the tool-use card. Clicking the path does nothing — it does not open the file in the editor, nor does it expand/render the markdown inline. The user must manually copy the path and run code <path> in a terminal to read the plan.
This breaks the core loop of Plan mode, which requires the user to read, review, and approve the plan before exiting Plan mode.
Environment
- Extension:
moonshot-ai.kimi-code
- OS: macOS (also reproducible on Windows/Linux per community reports)
- CLI/server version: latest stable
Actual behavior
Nothing happens. The path is non-interactive plain text. The file content shown in the OUT diff view is often truncated or insufficient for review. The user must copy the absolute path and open it externally.
Related issues
Suggested fix
Use VS Code webview message passing (postMessage) or a vscode://file/ URI so that clicking the path triggers vscode.open with the correct file:// URI. Alternatively, render the full plan markdown directly in the chat bubble, similar to how Codex handles plans.
What steps can reproduce the bug?
Steps to reproduce
- Start a new task in VS Code with the Kimi Code extension.
- Switch to Plan mode.
- Ask Kimi to create a plan (e.g. "Plan a refactor of the auth module").
- Wait for Kimi to generate the plan. It will emit a
WriteFile call targeting ~/.kimi/plans/<slug>.md.
- In the chat webview, click on the rendered file path under the IN/OUT card.
What is the expected behavior?
Expected behavior
Clicking the file path should open the plan file in a VS Code editor tab (or at minimum expand the file content inline in the chat), so the user can read the full plan without leaving the IDE.
Additional information
No response
What version of Kimi Code CLI is running?
moonshot-ai.kimi-code@0.5.10
Which open platform/subscription were you using?
Kimi Coding Plan
Which model were you using?
kimi-for-coding
What platform is your computer?
Darwin 23.0.0 arm64 arm
What issue are you seeing?
Bug description
In Plan mode, when Kimi writes a plan file (e.g.
~/.kimi/plans/<name>.md), the VS Code extension chat webview renders the absolute path as plain text in the tool-use card. Clicking the path does nothing — it does not open the file in the editor, nor does it expand/render the markdown inline. The user must manually copy the path and runcode <path>in a terminal to read the plan.This breaks the core loop of Plan mode, which requires the user to read, review, and approve the plan before exiting Plan mode.
Environment
moonshot-ai.kimi-codeActual behavior
Nothing happens. The path is non-interactive plain text. The file content shown in the
OUTdiff view is often truncated or insufficient for review. The user must copy the absolute path and open it externally.Related issues
Suggested fix
Use VS Code webview message passing (
postMessage) or avscode://file/URI so that clicking the path triggersvscode.openwith the correctfile://URI. Alternatively, render the full plan markdown directly in the chat bubble, similar to how Codex handles plans.What steps can reproduce the bug?
Steps to reproduce
WriteFilecall targeting~/.kimi/plans/<slug>.md.What is the expected behavior?
Expected behavior
Clicking the file path should open the plan file in a VS Code editor tab (or at minimum expand the file content inline in the chat), so the user can read the full plan without leaving the IDE.
Additional information
No response