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

[FEATURE]: Permissions "allow for session" #9275

New Issue
Open
opened 2026-02-16 18:12:03 -05:00 by yindo · 2 comments
yindo commented 2026-02-16 18:12:03 -05:00
Owner
Copy Link
Copy Source

Originally created by @jacksontj on GitHub (Feb 13, 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

When I am working in a specific repo it is very common that I want to give the model access to some other repo for the specific task (i.e. argo repo vs helm chart repo). Today when I get a permissions popup the options are:

  • Allow once
  • Always Allow
  • Deny

What I'm suggesting is an option for "allow for this session" -- that way I can grant access to a given repo for the duration of my session/task without having to grant permissions always.

Originally created by @jacksontj on GitHub (Feb 13, 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 When I am working in a specific repo it is very common that I want to give the model access to some other repo for the specific task (i.e. argo repo vs helm chart repo). Today when I get a permissions popup the options are: * Allow once * Always Allow * Deny What I'm suggesting is an option for "allow for this session" -- that way I can grant access to a given repo for the duration of my session/task without having to grant permissions always.
yindo added the discussion label 2026-02-16 18:12:03 -05:00
yindo commented 2026-02-16 18:12:03 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Feb 13, 2026):

This issue might be a duplicate of #10863: Feature: Add "Save Permanently" option to permission prompts.

Both issues discuss enhancing the permission prompt options. #10863 proposes a restructured permission model with a "Session" option (your specific request) along with a "Permanent" option for persisting to config.

Please review #10863 to see if it addresses your needs or if your use case has additional requirements.

@github-actions[bot] commented on GitHub (Feb 13, 2026): This issue might be a duplicate of #10863: Feature: Add "Save Permanently" option to permission prompts. Both issues discuss enhancing the permission prompt options. #10863 proposes a restructured permission model with a "Session" option (your specific request) along with a "Permanent" option for persisting to config. Please review #10863 to see if it addresses your needs or if your use case has additional requirements.
yindo commented 2026-02-16 18:12:03 -05:00
Author
Owner
Copy Link
Copy Source

@jacksontj commented on GitHub (Feb 13, 2026):

Based on the update from the bot #10863 seems related; but would actually change this probably to a bug. If the Always Allow is for the session it is not clear from the prompt ("always" sounds like forever). So if that is in fact a session-only "always" then this feature request would be to make that clearer

@jacksontj commented on GitHub (Feb 13, 2026): Based on the update from the bot #10863 seems related; but would actually change this probably to a bug. If the `Always Allow` is for the session it is *not* clear from the prompt ("always" sounds like forever). So if that is in fact a session-only "always" then this feature request would be to make that clearer
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#9275
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?