Skip to content

[FEATURE]: Allow editing the "always" permission pattern before confirming #24795

Closed as not planned

Description

@jamescw19

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 a permission prompt appears and I choose "always", the pattern used is auto-generated by the tool. Sometimes that pattern is too broad or too narrow for what I actually want.

For example, in the screenshot below I wanted to run psql commands, but these were being swallowed by rtk * commands. I use rtk as a plugin, but I don't want to enable all commands.

Image

It would be useful to be able to edit the pattern in the prompt before confirming, so I can tune it without having to manually open opencode.json after the fact. In this case I wanted to be able to allow rtk psql * commands only for the duration of the session.

Activity

  1. added
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on Apr 28, 2026
  2. github-actions commented on Apr 28, 2026

    @github-actions
    Contributor

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

  3. removed
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on May 3, 2026
  4. Grelo4ka commented on Jun 16, 2026

    @Grelo4ka

    That'd be indeed nice to have!

  5. n-prat commented on Jun 30, 2026

    @n-prat

    Also hitting this because using rtk.

    Allowing to edit the "always allow" command manually would work, but ideally it should be more a ignored_prefixes: ["rtk"] in the config or something like that to have the prompt directly be the intended command.

    edit: above is maybe duped with #29311 and a bunch of others related

  6. github-actions commented on Aug 30, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions