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

Persist 'always' permission approvals to disk #7676

New Issue
Open
opened 2026-02-16 18:07:54 -05:00 by yindo · 3 comments
yindo commented 2026-02-16 18:07:54 -05:00
Owner
Copy Link
Copy Source

Originally created by @felipemadero on GitHub (Jan 26, 2026).

Originally assigned to: @rekram1-node on GitHub.

When selecting "always" on a permission prompt, the approval only persists in memory for the session. The code to save it to disk exists but is commented out.

Since users already manage config files manually (by default there is no config file and all permissions are allowed), there's no reason to block persistence on having a UI.

Originally created by @felipemadero on GitHub (Jan 26, 2026). Originally assigned to: @rekram1-node on GitHub. When selecting "always" on a permission prompt, the approval only persists in memory for the session. The code to save it to disk exists but is commented out. Since users already manage config files manually (by default there is no config file and all permissions are allowed), there's no reason to block persistence on having a UI.
yindo commented 2026-02-16 18:07:54 -05:00
Author
Owner
Copy Link
Copy Source

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

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

  • #6020: Permission selection not respected - same 'always accept' not persisting issue
  • #9554: 'Always allow' TUI approvals override restrictions - reveals critical scoping issues with in-memory persistence
  • #9971: OAuth Enhancements including YOLO Mode - comprehensive feature proposal with persistent 'always' approvals to config.json

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

@github-actions[bot] commented on GitHub (Jan 26, 2026): This issue might be a duplicate of existing issues. Please check: - #6020: Permission selection not respected - same 'always accept' not persisting issue - #9554: 'Always allow' TUI approvals override restrictions - reveals critical scoping issues with in-memory persistence - #9971: OAuth Enhancements including YOLO Mode - comprehensive feature proposal with persistent 'always' approvals to config.json Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 18:07:54 -05:00
Author
Owner
Copy Link
Copy Source

@ThomasCarca commented on GitHub (Feb 12, 2026):

This would be a good quality of life feature. Having to manually edit the config file to persist allowed commands between session is a bit of a hassle.

@ThomasCarca commented on GitHub (Feb 12, 2026): This would be a good quality of life feature. Having to manually edit the config file to persist allowed commands between session is a bit of a hassle.
yindo commented 2026-02-16 18:07:54 -05:00
Author
Owner
Copy Link
Copy Source

@tredondo commented on GitHub (Feb 12, 2026):

For me in Desktop, the "Allow always" approval isn't persistent at all. OC asks for the same permission over and over.

This should be a P1 because it makes it impossible to leave the agent working unattended in a sandbox.

@thdxr

Image
@tredondo commented on GitHub (Feb 12, 2026): For me in Desktop, the "Allow always" approval isn't persistent at all. OC asks for the same permission over and over. This should be a P1 because it makes it impossible to leave the agent working unattended in a sandbox. @thdxr <img width="1177" height="207" alt="Image" src="https://github.com/user-attachments/assets/e6894a7e-0be1-4d2c-8978-b4f5e6d31e1d" />
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
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#7676
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?