sorry opened by accident #8170

Closed
opened 2026-02-16 18:09:19 -05:00 by yindo · 1 comment
Owner

Originally created by @kehao95 on GitHub (Jan 31, 2026).

Originally assigned to: @thdxr on GitHub.

opened by accident

Originally created by @kehao95 on GitHub (Jan 31, 2026). Originally assigned to: @thdxr on GitHub. opened by accident
yindo closed this issue 2026-02-16 18:09:19 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 31, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #10640: [FEATURE]: Intercept known Bash tool call patterns and replace them with specialized tools - proposes auto-allowing read-only operations without approval
  • #11397: [FEATURE]: Support regex in permissions configuration - seeks to reduce repetitive permission rules via regex patterns
  • #8463: [FEATURE]: Add --dangerously-skip-permissions (aka YOLO mode) - proposes auto-allowing trusted workflows
  • #10238: [FEATURE]: Safer default for build agent: prompt on destructive bash commands - inverse approach suggesting read-only commands shouldn't require approval
  • #7407: [FEATURE]: Allow skills and commands to define scoped permission overrides - similar solution for reducing approval friction for known-safe commands

Feel free to ignore if your specific use case differs from these.

@github-actions[bot] commented on GitHub (Jan 31, 2026): This issue might be a duplicate of existing issues. Please check: - #10640: [FEATURE]: Intercept known Bash tool call patterns and replace them with specialized tools - proposes auto-allowing read-only operations without approval - #11397: [FEATURE]: Support regex in permissions configuration - seeks to reduce repetitive permission rules via regex patterns - #8463: [FEATURE]: Add `--dangerously-skip-permissions` (aka YOLO mode) - proposes auto-allowing trusted workflows - #10238: [FEATURE]: Safer default for build agent: prompt on destructive bash commands - inverse approach suggesting read-only commands shouldn't require approval - #7407: [FEATURE]: Allow skills and commands to define scoped permission overrides - similar solution for reducing approval friction for known-safe commands Feel free to ignore if your specific use case differs from these.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8170