Permission prompt offers misleading "allow commands starting with ..." prefix

Open 💬 2 comments Opened Apr 5, 2026 by sigrorn

What version of the IDE extension are you using?

26.325.31654

What subscription do you have?

Plus

Which IDE are you using?

VSCode 1.113.0

What platform is your computer?

Windows

What issue are you seeing?

Occasionally, I'm being asked whether to allow to run a command, one of the options is "Allow commands starting with ...", but inside that prompt, you have the full command line including all it's parameters. That makes little to no sense -- one of the effects is that I just got asked 3 separate times whether I'd like to allow commands starting with

& 'C:\Program Files\GitHub CLI\gh.exe' issue view 41 --repo mychat/mychat --comments
& 'C:\Program Files\GitHub CLI\gh.exe' issue view 42 --repo myuser/mychat --comments
& 'C:\Program Files\GitHub CLI\gh.exe' issue view 43 --repo myuser/mychat --comments

Why could I not simply once allow executions of all commands starting with 'C:\Program Files\GitHub CLI\gh.exe'?

What steps can reproduce the bug?

happens during analysis runs, where codex tries to look through a code-base and issues -- it just wants to call, say, gh with different parameters, but always asking me again whether to allow it.

What is the expected behavior?

Asking my permission is good, but maybe change the options to:
1) allow this command <full commandline> just this once?
2) always allow command <commandname>?
3) do not allow

Additional information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗