-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Closed
Description
Summary
Add a "YOLO Mode" that allows users to skip all permission prompts, similar to Claude Code's --dangerously-skip-permissions flag.
Use Case: Power users who trust OpenCode and want faster workflow without constant permission confirmations.
Proposed Implementation
Backend
- Add
OPENCODE_YOLOenvironment variable flag - Add
yolo: booleanconfig option inopencode.json - Modify
PermissionNext.ask()to auto-approve when YOLO mode is enabled - Add runtime state that can be toggled without restart
Server API
GET /config/yolo- Check current YOLO mode statusPOST /config/yolo- Toggle YOLO mode at runtime
CLI
- Add
--yoloor--dangerously-skip-permissionsflag - Add
opencode yolo status/enable/disablecommands - Example:
opencode --yoloorOPENCODE_YOLO=true opencode
Desktop App
- Add "Danger Zone" tab in Settings dialog
- Toggle switches for:
- This Session Only - Resets on restart
- Always Enabled - Persists to config
- Prominent warning messaging about the risks
Safety Considerations
- Clear warning messaging in both CLI and Desktop
- Not enabled by default
- Session-based option available (does not persist across restarts)
- Still respects explicit
denyrules in config
Dependencies
- Depends on feat: Multi-Account OAuth Rotation with Settings UI #9068 (Multi-Account OAuth) for the Settings UI infrastructure
Acceptance Criteria
-
OPENCODE_YOLO=trueenv var enables YOLO mode -
opencode --yoloCLI flag works -
opencode yolo status/enable/disablecommands work - Config option
"yolo": trueinopencode.jsonworks - Desktop Settings shows Danger Zone tab with toggle
- Toggle updates server state immediately
- All permission prompts are auto-approved in YOLO mode
- Clear warning messaging is displayed
- Session vs Permanent mode options available
Implementation
PR #9073 implements all features described above.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels