chat, config: /yolo, a yolo choice in permissions, and turn on yolo on every permission question #1074

Problem

"Run without asking" has three names and two of them are hidden:

• Flag. --yolo opens the gate for a whole process and must be typed at launch.
• Status line. It shows a YOLO badge.
• Settings. The Safety row ask before running offers prompt / allow / deny. The word a person knows, yolo, is not a choice: they must know that allow is YOLO.
• Commands. No command switches it on dev. A person who wants to stop being asked mid-conversation has to open /settings, find Safety, and cycle a row whose values don't use the word the badge uses.

Ask

1. /yolo command. It toggles the current conversation between asking and YOLO, and says the resulting posture in one line. With an argument it sets a posture by name. It must be discoverable in / completion and /help.

2. yolo in permissions. The Safety row offers yolo as a named choice, with one vocabulary everywhere: the row, the badge, /status, /status --json, the manual. Options:

   • a. Rename allow → yolo on the row. Keep allow accepted on disk and in --approvals-style inputs as an alias, so saved profiles keep meaning the same thing.
   • b. Keep allow and add yolo as a displayed alias that writes allow.
   • Recommended: a. The badge already says YOLO, and a person should see one word for one state.

3. Same safety as --yolo. Named tool exceptions, shell rules and the critical-command floor still apply. /yolo must not be a way past the floor.

4. Scope. The command changes the current conversation, live, sticky, and restored on /resume. The Safety row stays the install default. Both say which one they changed.

5. YOLO from every permission question. Today the consent card (AnswerOptions(QuestionConsent), internal/session/answers.go) offers 1 allow once · 2 always (this tool, this session) · 3 deny. A person who is tired of being asked has to leave the question to find the setting. Add a fourth answer on every permission question: 4 turn on yolo.

   • It answers this call with allow, and switches the conversation's posture to YOLO: the same state /yolo sets, sticky and restored on /resume.
   • It is marked Widening, drawn apart from the others like always, and never the default cursor, so muscle memory on 1 cannot land on it.
   • The card's result line says what changed, e.g. allowed · yolo on for this conversation · /yolo to turn it off.
   • The critical floor is untouched. A floor command's card does not offer turn on yolo, since the floor asks whatever the posture is.
   • It applies on every surface that draws the consent question (chat card, home, the remote/phone sheet, a task room), and on the wire through the same answer set, so a replica offers exactly the same four.
   • Questions that borrow the consent lane for something that is not a tool call (e.g. the stuck-turn question, which already drops always) don't offer it either.

Related

• UX changes: home navigation and consistent message-box controls #1071 (draft). A per-conversation approvals posture with /approvals (alias /yolo) and an alt+y wheel. If it lands, it covers item 1 and most of 4. This issue then tracks item 2 (the yolo word in the permissions row and /status) plus confirming /yolo shows in completion and help.
• tui3, config: the gate row lands on the conversation you are in, and /status names the gate #1063 (merged). Changing the Safety row now reaches the running gate, and /status names the gate as prompt / allow / deny, which is the vocabulary item 2 would change.
• headless and --yolo cells cannot answer the approval floor, so rm -rf stalls a bench cell forever #1035. Headless and --yolo runs still can't answer the approval floor. Out of scope here, but the floor behaviour in item 3 must stay consistent with whatever that issue decides.

Acceptance

• /yolo in a live conversation flips the next tool call's gate, shows the posture, survives /resume, and still asks on a floor command.
• /settings → Safety shows yolo as a choice. An existing profile with allow reads as yolo with no migration step.
• Badge, /status, JSON and the manual use the same word.
• Every permission card that is not a floor command offers turn on yolo. Picking it runs the call, flips the posture, and the next non-floor call runs without a card.
• Tests for each, plus the manual law.

Drafted with CodeAF · reviewed and owned by the author

Drafted with CodeAF · reviewed and owned by the author