MoonshotAI / MoonshotAI/kimi-cli
Add Shift+Tab shortcut to toggle YOLO (auto-accept) mode
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11.4k
- Forks
- 1.3k
- Avg merge
- 9h 47m
- Merged PRs (30d)
- 2
Description
What feature would you like to see?
Add a Shift + Tab keyboard shortcut that toggles YOLO mode (auto-accept / skip-confirmation mode) from inside an active kimi-cli session.
This mirrors Claude Code's UX, where Shift + Tab cycles between permission modes (normal → auto-accept-edits → plan), giving the user a one-keystroke way to opt into a more autonomous run without restarting the session or editing config.
Proposed UX
- Pressing
Shift + Tabcycles the current session's permission mode, e.g.:- Normal — confirm before every tool call / file edit (current default)
- YOLO / auto-accept — auto-approve tool calls and edits, no prompts
- (optional) Plan-only — model can read and think but cannot mutate state
- The active mode is shown persistently in the status bar / prompt line, so the user can tell at a glance which mode they're in.
- Mode is session-scoped and resets when the session ends — it should never persist silently across restarts.
Why it matters
- For trusted, repetitive workflows (e.g. refactors, batch edits, scripted runs) the per-action confirmation prompt is the main source of friction.
- A keystroke toggle is much faster than a slash command and matches user muscle memory from Claude Code.
- Pairing it with an always-visible mode indicator keeps it safe: users opt in deliberately and can see they're in YOLO mode at all times.
Open questions
- Should YOLO mode also auto-approve shell commands (
Bash) or only file edits? Suggest splitting: e.g.Shift+Tabonce = auto-accept edits; twice = auto-accept everything. - Should there be a config option to disable the shortcut entirely for users on shared / production machines?
- Should the mode survive
/resumeor always reset to Normal on resume?
Happy to prototype if the team is interested.
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
The issue names no files or tests. Start by locating active kimi-cli session keyboard handling, permission prompts, and status-bar or prompt-line rendering; review how /resume and Bash permissions are represented. Done means Shift+Tab changes a session-scoped mode, the current mode is visible, and the chosen reset and shell-command behavior are covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100