MoonshotAI / MoonshotAI/kimi-cli

[VSCode Extension] Plan mode file path not clickable in chat webview

Open
#2,317 4 comments 1 reaction 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?

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
  • #1672 — requests rendering the plan inline instead of as a file path (complementary request).
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
  1. Start a new task in VS Code with the Kimi Code extension.
  2. Switch to Plan mode.
  3. Ask Kimi to create a plan (e.g. "Plan a refactor of the auth module").
  4. Wait for Kimi to generate the plan. It will emit a WriteFile call targeting ~/.kimi/plans/<slug>.md.
  5. 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

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

Start by tracing how the VS Code extension chat webview renders file paths in the tool-use IN/OUT cards, then inspect its webview message handling. Done means clicking a plan path opens the file in a VS Code editor, or renders its full content inline, with behavior verified on the affected platforms.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
frontend, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.