What version of Kimi Code CLI is running?
0.20.1
Which open platform/subscription were you using?
Kimi Code (OAuth)
Which model were you using?
K2.7 Code
What platform is your computer?
Darwin 27.0.0 arm64 arm
What issue are you seeing?
Kimi-CLI doesn't respect "Approve for this session" option when working. Even though I give it permission for the session, it keeps asking for the same exact permission every single time and it is extremely frustrating to work with. For example when you want it to read a code base, it keeps asking for read permissions for every single file.
What steps can reproduce the bug?
- Give kimi-cli and instruction
- kimi-cli asks for permission
- Repeat
What is the expected behavior?
If I give permission for the session, it shouldn't ask me for it over and over again.
Additional information
This problem is not something new, it existed well before version 0.15. Also it is system or terminal independent. I have the same problem both on my MacOS machine and Windows machine. There is a similar issue #2448 , but since that is related to YOLO mode, I have created a separate bug report.
What version of Kimi Code CLI is running?
0.20.1
Which open platform/subscription were you using?
Kimi Code (OAuth)
Which model were you using?
K2.7 Code
What platform is your computer?
Darwin 27.0.0 arm64 arm
What issue are you seeing?
Kimi-CLI doesn't respect "Approve for this session" option when working. Even though I give it permission for the session, it keeps asking for the same exact permission every single time and it is extremely frustrating to work with. For example when you want it to read a code base, it keeps asking for read permissions for every single file.
What steps can reproduce the bug?
What is the expected behavior?
If I give permission for the session, it shouldn't ask me for it over and over again.
Additional information
This problem is not something new, it existed well before version 0.15. Also it is system or terminal independent. I have the same problem both on my MacOS machine and Windows machine. There is a similar issue #2448 , but since that is related to YOLO mode, I have created a separate bug report.