anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[FEATURE]: Add --dangerously-skip-permissions (aka YOLO mode) #5796

New Issue
Open
opened 2026-02-16 17:56:57 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 17:56:57 -05:00
Owner
Copy Link
Copy Source

Originally created by @surma on GitHub (Jan 14, 2026).

Originally assigned to: @thdxr on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Problem

When using OpenCode for automated workflows or in trusted environments, permission prompts can interrupt the flow and require manual intervention. This is particularly frustrating when you trust the agent and want it to operate autonomously.

Proposed Solution

This is already kinda possible with permissions env variable, but I feel like dedicated flag is nice because:

  • It matches Claude Code
  • It allows to show a warning in the UI that you are in YOLO mode

Usage

# CLI flag
opencode --dangerously-skip-permissions

# Environment variable
OPENCODE_DANGEROUSLY_SKIP_PERMISSIONS=true opencode

# With run command
opencode run --dangerously-skip-permissions "do something"

Behavior

  • Auto-allows all ask permission prompts
  • Explicit deny rules are still respected
  • Shows "△ YOLO mode" warning in the TUI (home screen, footer, and sidebar) to indicate the mode is active

Why This Belongs in OpenCode

This feature improves the developer experience for trusted workflows while maintaining safety through:

  1. Clear naming that indicates danger (dangerously-skip-permissions)
  2. Visual warnings when active
  3. Respect for explicit deny rules
  4. Similar to Claude Code's implementation, which users find valuable

Implementation

PR #7137 implements this feature with changes to:

  • Flag system to support the environment variable
  • Permission system to bypass ask prompts when enabled
  • CLI commands to accept the flag
  • TUI to show visual warnings when active
Originally created by @surma on GitHub (Jan 14, 2026). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request ## Problem When using OpenCode for automated workflows or in trusted environments, permission prompts can interrupt the flow and require manual intervention. This is particularly frustrating when you trust the agent and want it to operate autonomously. ## Proposed Solution This is already kinda possible with permissions env variable, but I feel like dedicated flag is nice because: - It matches Claude Code - It allows to show a warning in the UI that you are in YOLO mode ### Usage ```bash # CLI flag opencode --dangerously-skip-permissions # Environment variable OPENCODE_DANGEROUSLY_SKIP_PERMISSIONS=true opencode # With run command opencode run --dangerously-skip-permissions "do something" ``` ### Behavior - Auto-allows all `ask` permission prompts - Explicit `deny` rules are still respected - Shows "△ YOLO mode" warning in the TUI (home screen, footer, and sidebar) to indicate the mode is active ### Why This Belongs in OpenCode This feature improves the developer experience for trusted workflows while maintaining safety through: 1. Clear naming that indicates danger (`dangerously-skip-permissions`) 2. Visual warnings when active 3. Respect for explicit deny rules 4. Similar to Claude Code's implementation, which users find valuable ## Implementation PR #7137 implements this feature with changes to: - Flag system to support the environment variable - Permission system to bypass `ask` prompts when enabled - CLI commands to accept the flag - TUI to show visual warnings when active
yindo added the discussion label 2026-02-16 17:56:57 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label discussion
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#5796
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?