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 + Tab cycles 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+Tab once = 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
/resume or always reset to Normal on resume?
Happy to prototype if the team is interested.
What feature would you like to see?
Add a
Shift + Tabkeyboard 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 + Tabcycles 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
Shift + Tabcycles the current session's permission mode, e.g.:Why it matters
Open questions
Bash) or only file edits? Suggest splitting: e.g.Shift+Tabonce = auto-accept edits; twice = auto-accept everything./resumeor always reset to Normal on resume?Happy to prototype if the team is interested.