Description
YOLO mode (auto-approve permission prompts) can only be turned on at startup, with the
--yolo flag or ALTIMATE_CLI_YOLO=1. There's no way to enable it once you're already
in a conversation.
Use Case
You start a session normally, then hit a stretch of work where you're approving every
step and just want it to run. Today the only option is to quit, relaunch with --yolo,
and lose your context — which also turns it on globally for the whole process rather than
for the one conversation you're working in.
The reverse case matters too: if you launched with --yolo and want to go back to being
asked, there's no way to do that without restarting either.
Proposed Solution
A ctrl+y toggle in the TUI:
- Visible hint on the chat panel, and a clear indicator while it's on.
- Enabling asks for confirmation; disabling is immediate — turning a dangerous mode off
shouldn't be harder than leaving it on.
- Scoped to the current conversation and any subagents it spawns, not the whole process.
- An explicit toggle should win over the
--yolo default in both directions.
- Not persisted, so reopening an old conversation can't silently put you back in it.
The confirmation should be honest about scope: configured deny rules (DROP DATABASE and
friends) are refused server-side before the TUI ever sees them, so they stay blocked. What
actually stops being asked is the "ask"-level stuff — rm -rf, force pushes, reading
.env.
Alternatives Considered
Storing the "don't ask" decision on the session server-side instead of in the TUI.
Rejected: session rules are last-match-wins and are applied after the safety rules, so an
allow-all written there would override the DROP DATABASE denies. It also wouldn't reach
subagents, which deliberately inherit only the parent's restrictions.
Description
YOLO mode (auto-approve permission prompts) can only be turned on at startup, with the
--yoloflag orALTIMATE_CLI_YOLO=1. There's no way to enable it once you're alreadyin a conversation.
Use Case
You start a session normally, then hit a stretch of work where you're approving every
step and just want it to run. Today the only option is to quit, relaunch with
--yolo,and lose your context — which also turns it on globally for the whole process rather than
for the one conversation you're working in.
The reverse case matters too: if you launched with
--yoloand want to go back to beingasked, there's no way to do that without restarting either.
Proposed Solution
A
ctrl+ytoggle in the TUI:shouldn't be harder than leaving it on.
--yolodefault in both directions.The confirmation should be honest about scope: configured deny rules (DROP DATABASE and
friends) are refused server-side before the TUI ever sees them, so they stay blocked. What
actually stops being asked is the "ask"-level stuff —
rm -rf, force pushes, reading.env.Alternatives Considered
Storing the "don't ask" decision on the session server-side instead of in the TUI.
Rejected: session rules are last-match-wins and are applied after the safety rules, so an
allow-all written there would override the DROP DATABASE denies. It also wouldn't reach
subagents, which deliberately inherit only the parent's restrictions.