[ENHANCEMENT] Add YOLO mode for explicit broad auto-approval - #137

Related GitHub Issue

Closes: #132

Description

This PR adds an explicit YOLO mode to the auto-approval system.

Key changes:

• Adds yoloMode to global settings/state plumbing.
• Updates checkAutoApproval so YOLO mode approves broad tool, MCP, and command categories while preserving denied command prefixes and protected-write boundaries.
• Keeps follow-up asks/manual choices out of YOLO auto-approval and disables follow-up auto-approval countdowns while YOLO mode is active.
• Updates the chat auto-approval dropdown so YOLO appears active, individual quick controls are locked, and the displayed enabled count reflects the effective YOLO state.
• Updates auto-approval settings to expose the YOLO checkbox and lock granular controls while YOLO is active, using cachedState rather than direct live state mutation.
• Adds tests for YOLO decision behavior and follow-up suggestion behavior.

Reviewer focus:

• Whether the scope of YOLO approval is acceptable for Zoo Code.
• Whether the UI language makes the risk clear without adding nagging pop-ups.
• Whether protected writes and denied command prefixes remain respected.
• Whether locking granular controls while YOLO is active is preferable to letting users edit them behind the effective YOLO override.

Test Procedure

From the Zoo Code worktree:

pnpm lint
pnpm check-types
pnpm --filter zoo-code test -- core/auto-approval/__tests__/checkAutoApproval.spec.ts
pnpm --filter @roo-code/vscode-webview test -- src/components/chat/__tests__/FollowUpSuggest.spec.tsx src/hooks/__tests__/useAutoApprovalState.spec.ts

Manual verification recommended:

• Enable YOLO mode in settings.
• Confirm allowed read/write/MCP/mode/subtask/command flows proceed without repeated confirmations.
• Confirm denied command prefixes are still blocked.
• Confirm protected writes still require explicit protected-write configuration.
• Confirm follow-up questions still wait for user input.

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue.
• Scope: My changes are focused on the linked issue.
• Self-Review: I have performed a thorough self-review of my code.
• Testing: New and/or updated tests have been added to cover my changes.
• Documentation Impact: I have considered if my changes require documentation updates.
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshots / Videos

TODO: Attach screenshots of the YOLO mode setting and auto-approval dropdown.

Documentation Updates

Yes. User-facing docs should explain what YOLO mode approves, what it still blocks, and when users should avoid enabling it.

Additional Notes

Related but not duplicate:

• [ENHANCEMENT] Reduce approval-control flash for auto-approved read-only asks #102
• [ENHANCEMENT] Tighten Task.ask sequencing for auto-approved read-only asks #105

This PR deliberately does not auto-answer follow-up questions in YOLO mode.

Get in Touch

Discord: coorbin