Skip to content

Add YOLO mode for CLI and TUI sessions#9392

Open
Githubguy132010 wants to merge 12 commits intoKilo-Org:mainfrom
Githubguy132010:feature/cli/yolo-mode
Open

Add YOLO mode for CLI and TUI sessions#9392
Githubguy132010 wants to merge 12 commits intoKilo-Org:mainfrom
Githubguy132010:feature/cli/yolo-mode

Conversation

@Githubguy132010
Copy link
Copy Markdown
Contributor

@Githubguy132010 Githubguy132010 commented Apr 22, 2026

Context

Add a YOLO mode that skips tool permission prompts, without changing the existing meaning of --auto for autonomous runs.

Implementation

Added a new --yolo flag to kilo run and a /yolo toggle in the TUI. For kilo run, YOLO auto-approves permission requests without changing --auto. In the TUI, YOLO is session-scoped and transient: it auto-replies once to permission requests for the active session instead of persisting a wildcard session rule. That keeps agent-level denies intact, avoids leaking YOLO across other sessions, and lets /yolo behave like a real toggle. A small Home tip was also added so the mode is easier to discover.

Screenshots

before after
N/A N/A

How to Test

  • Run kilo run --yolo \"check the repo\" and confirm permission prompts are auto-approved.
  • Start kilo --yolo, open a new session, and confirm repeated permission prompts in that session are auto-approved.
  • In a TUI session, run /yolo to toggle session-scoped YOLO mode on and off.
  • Confirm disabling /yolo keeps it disabled.
  • Confirm plan-mode or agent-level denied tools remain denied while YOLO is enabled.
  • Confirm navigating to a different session does not silently enable YOLO there.
  • Run bun test test/cli/yolo-mode.test.ts
  • Run bun test test/cli/tui/thread.test.ts
  • Run bun run typecheck

Get in Touch

Thomas Brugman (thomas07374) on Kilo Code Discord.

- Add --yolo CLI flag to auto-approve tools without prompts
- Add /yolo TUI command to toggle YOLO mode mid-session
- Replace auto-mode tests with yolo-mode tests
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ff9037c86c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread packages/opencode/src/kilocode/cli/cmd/tui/app.tsx Outdated
- Adds --yolo CLI flag
- Allows tools to run without permission prompts
- Creates session with wildcard permissions
Comment thread packages/opencode/src/cli/cmd/tui/component/prompt/index.tsx Outdated
Comment thread packages/opencode/src/kilocode/cli/cmd/tui/app.tsx Outdated
@kilo-code-bot
Copy link
Copy Markdown
Contributor

kilo-code-bot Bot commented Apr 22, 2026

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (1 files)
  • packages/opencode/test/cli/tui/yolo.test.ts

Reviewed by gpt-5.4-20260305 · 1,478,148 tokens

Wait for first permission request and reply once instead of allowing all tools at session creation
Preserve yolo behavior across session restarts via yoloSessionID
Comment thread packages/opencode/src/kilocode/cli/cmd/tui/app.tsx Outdated
Comment thread packages/opencode/src/kilocode/cli/cmd/tui/app.tsx Outdated
Separates yolo session tracking into dedicated module for cleaner state management
- Add kilocode_change comment to import for fork merge compatibility
Comment thread packages/opencode/src/kilocode/cli/cmd/tui/app.tsx Outdated
Comment thread packages/opencode/src/kilocode/cli/cmd/tui/yolo.ts Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants