MoonshotAI / MoonshotAI/kimi-code
Permissions names are dangerously confusing
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 7.5k
- Forks
- 1.2k
- Avg merge
- 11h 53m
- Merged PRs (30d)
- 350
Description
What version of Kimi Code is running?
0.27.0
Which open platform/subscription were you using?
kimi oauth
Which model were you using?
K3
What platform is your computer?
WSL
What issue are you seeing?
Auto and YOLO permissions are backwards from what people probably expect:
What steps can reproduce the bug?
/permissions
What is the expected behavior?
In a clean room I would just swap Auto and YOLO labels, but since you've shipped with those already, probably choosing completely new ones to avoid confusion is best
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 with the /permissions command and inspect where the Auto and YOLO labels are presented. Determine replacement names that avoid the reported confusion while preserving the existing permission behavior; done means the command clearly distinguishes the two modes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authorization, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100