MoonshotAI / MoonshotAI/kimi-cli
新版本现在连@filename都不支持了？ || The new version does not even support @filename now?
Open
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?
0.11.0
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?
你们这个升级，之前的方式不能用了？
What steps can reproduce the bug?
。。。
What is the expected behavior?
No response
Additional information
No response
What version of Kimi Code CLI is running?
0.11.0
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?
With your upgrade, the previous method can no longer be used?
What steps can reproduce the bug?
. . .
What is the expected behavior?
No response
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in Kimi Code CLI 0.11.0 using the reported @filename syntax, then compare its behavior with the previous version. The report does not name a source file, test, platform, model, reproduction steps, or expected behavior; done means the intended @filename support works again or the changed behavior is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100