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

[FEATURE]: Allow editing custom patterns in the "Allow always" permission flow

• I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Right now, when OpenCode asks for permission to run a command and I choose Allow always, the TUI only lets me confirm the server-suggested pattern(s). That works for simple cases, but it is too limiting for commands where the suggested rule is much broader than what I actually want to allow.

For example, if the requested command is something like:

devcontainer exec ls

or:

docker exec -it app_foo cat /etc/hosts

the suggested "always allow" pattern may end up being broad, like:

docker *

What I want instead is a way to edit that rule before confirming, for example:

docker exec -it app_* cat *

That would make the feature much safer and more useful, because users could save a narrow session rule instead of being forced to choose between:

• a rule that is too broad
• approving the command every time with "Allow once"
• manually editing config outside the prompt

Suggested behavior:

• after selecting Allow always, open an editable textarea instead of a static confirm screen
• pre-fill it with the suggested pattern(s)
• allow one pattern per line
• if the edited patterns are submitted, store those for the session
• if the field is left empty, fall back to the current suggested pattern behavior

This would keep the current flow intact for simple cases, while making permission approvals much more practical for tools like docker, devcontainer, and similar wrapper commands.