Command permissions
Resolved 💬 5 comments Opened Sep 20, 2025 by matssk Closed Dec 14, 2025
💡 Likely answer: A maintainer (etraut-openai, contributor)
responded on this thread — see the highlighted reply below.
What feature would you like to see?
I would suggest three permissions for command line commands. Always block, Always ask and Always allow
This could come as options the first time it tries to run a command. For example if it tries to run 'git' you would see the options: "Allow once", "Always allow", "Always ask", "Always block", "Block once". Essentially what this would do is to add commands to a blacklist and a whitelist. Commands that are not on either a blacklist or a whitelist would be "always ask" so no need for an extra list for this.
Are you interested in implementing this feature?
_No response_
Additional information
_No response_
5 Comments
That would be useful, but it is important to be able to allow all command executions too, regardless of params, so not just "nl -ba packages/shared/src/services/base/base.service.ts" but something like "nl /"
Strongly support this. It is tedious to have to approve the same commands over and over.
If finer granularity is needed, perhaps parameters could be regexed. That is to say, you could approve the command
foo *OR some more strict regex wherefoo baris allowed butfoo bazis not.I'm going to close this in favor of #3085, which has more upvotes.
We have recently added a new preview feature called "rules" which implements this functionality. For details, refer to this documentation.
Page not found
@ziyuang, apologies for the stale link. Here's the updated link. I've also updated my original post.