MoonshotAI / MoonshotAI/kimi-cli

vscode插件中subagent修改的文件无法在改动栏显示, 非常不方便 || The files modified by subagent in the vscode plug-in cannot be displayed in the change column, which is very inconvenient.

Open
#1,889 0 comments 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.33.0

Which open platform/subscription were you using?

kimi coding plan

Which model were you using?

kimi-for-coding

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What issue are you seeing?

vscode插件中, subagents修改的文件无法在文件改动总览里看到, 非常不方便.

What steps can reproduce the bug?

运行任意任务, 强调使用subagent进行修改, 必现

What is the expected behavior?

No response

Additional information

No response


What version of Kimi Code CLI is running?

1.33.0

Which open platform/subscription were you using?

kimi coding plan

Which model were you using?

kimi-for-coding

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What issue are you seeing?

In the vscode plug-in, files modified by subagents cannot be seen in the file change overview, which is very inconvenient.

What steps can reproduce the bug?

Run any task, emphasize using subagent to make modifications, and it will appear.

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

Reproduce the issue in the VS Code plug-in with Kimi Code CLI 1.33.0 on Windows by running a task that asks a subagent to modify files. Trace how modified files are reported to the file-change overview, then verify that all subagent changes appear there.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, vscode
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.