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

[FEATURE]:Add "Accept for Session" Option for Permission Prompts #2268

New Issue
Closed
opened 2026-02-16 17:34:54 -05:00 by yindo · 6 comments
yindo commented 2026-02-16 17:34:54 -05:00
Owner
Copy Link
Copy Source

Originally created by @NickPaul41 on GitHub (Oct 24, 2025).

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

When approving Permission required to run this tool:, I currently have three options: accept, reject, and always. I do not want to set permissions as "always" (which persists across sessions), so I choose "accept." However, when Opencode executes the same command again, it re-prompts for permission each time.

I would like to add a fourth option: "Accept for Current Session". This would allow Opencode to run those commands again during the current session without re-prompting, while not persisting the permission in future sessions.

Benefits:

  • Reduces repetitive permission prompts during active work
  • Maintains security by not permanently storing permissions
  • Improves user experience and workflow efficiency
Originally created by @NickPaul41 on GitHub (Oct 24, 2025). 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 When approving `Permission required to run this tool:`, I currently have three options: accept, reject, and always. I do not want to set permissions as "always" (which persists across sessions), so I choose "accept." However, when Opencode executes the same command again, it re-prompts for permission each time. I would like to add a fourth option: "Accept for Current Session". This would allow Opencode to run those commands again during the current session without re-prompting, while not persisting the permission in future sessions. **Benefits:** - Reduces repetitive permission prompts during active work - Maintains security by not permanently storing permissions - Improves user experience and workflow efficiency
yindo added the discussion label 2026-02-16 17:34:54 -05:00
yindo closed this issue 2026-02-16 17:34:54 -05:00
yindo commented 2026-02-16 17:34:54 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Oct 24, 2025):

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

  • #2264: Feature request for persisting permission requests - discusses similar session-based permission handling concerns

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Oct 24, 2025): This issue might be a duplicate of existing issues. Please check: - #2264: Feature request for persisting permission requests - discusses similar session-based permission handling concerns Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 17:34:54 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Oct 24, 2025):

@NickPaul41 the "always" only lasts as long as the opencode instance runs it is held in memory and not persisted just so you know

This is non obvious and we are rethinking some of our ux around permissions

@rekram1-node commented on GitHub (Oct 24, 2025): @NickPaul41 the "always" only lasts as long as the opencode instance runs it is held in memory and not persisted just so you know This is non obvious and we are rethinking some of our ux around permissions
yindo commented 2026-02-16 17:34:54 -05:00
Author
Owner
Copy Link
Copy Source

@NickPaul41 commented on GitHub (Oct 24, 2025):

Oh that's perfect! I can close this then.

@NickPaul41 commented on GitHub (Oct 24, 2025): Oh that's perfect! I can close this then.
yindo commented 2026-02-16 17:34:54 -05:00
Author
Owner
Copy Link
Copy Source

@RomainLanz commented on GitHub (Dec 19, 2025):

the "always" only lasts as long as the opencode instance runs it is held in memory and not persisted just so you know

Sorry to bump this, but is there a way to reset this setting back to ask without exiting the session?

The timing of prompts sometimes overlaps with my typing, causing me to accidentally hit a and trigger "always accept" mode. Once that happens, OpenCode starts auto-approving everything, which can quickly spiral out of control.

For reference, Claude Code handles this nicely by allowing you to toggle between ask/auto-accept modes at any time using Shift+Tab and prompts use 1, 2, 3.

@RomainLanz commented on GitHub (Dec 19, 2025): > the "always" only lasts as long as the opencode instance runs it is held in memory and not persisted just so you know Sorry to bump this, but is there a way to reset this setting back to `ask` without exiting the session? The timing of prompts sometimes overlaps with my typing, causing me to accidentally hit a and trigger "always accept" mode. Once that happens, OpenCode starts auto-approving everything, which can quickly spiral out of control. For reference, Claude Code handles this nicely by allowing you to toggle between ask/auto-accept modes at any time using Shift+Tab and prompts use `1`, `2`, `3`.
yindo commented 2026-02-16 17:34:54 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Dec 19, 2025):

@RomainLanz Dax is redoing permissions UX rn i think it should help w/ this to a degree more improvements shipping soon

@rekram1-node commented on GitHub (Dec 19, 2025): @RomainLanz Dax is redoing permissions UX rn i think it should help w/ this to a degree more improvements shipping soon
yindo commented 2026-02-16 17:34:54 -05:00
Author
Owner
Copy Link
Copy Source

@RomainLanz commented on GitHub (Jan 3, 2026):

Should I open another issue? Because it seems there a many improvement but nothing related to this.

@RomainLanz commented on GitHub (Jan 3, 2026): Should I open another issue? Because it seems there a many improvement but nothing related to this.
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#2268
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?