[Feature Request] Customizing bash command permissions.

In Q CLI, you are given two tool trust options: trust on a per-command basis, and trust on every command basis. However, for the execute_bash tool, it is very hard for developers to provide full trust to this tool, since there are a wide variety of bash commands. However, the user may want to give trust to some bash commands (for example, mkdir and cd for file navigation and directory creation). Giving the user customization options over which bash commands are acceptable will help increase developer trust with using Q CLI tools, especially in agent script usage where they trust certain parts of the script to run autonomously using bash commands, but don't trust every command.

If needed, I can help take a look at adding this functionality. I had done a small pr for Q CLI a month ago, and am eager to learn more about the codebase as well.

Thank you!

L’issue mentionne Q CLI, l’outil execute_bash et les options de confiance existantes par commande et pour chaque commande, mais n’indique aucun fichier ni test. Commencez par localiser execute_bash et ces chemins de gestion de la confiance ; le travail est terminé lorsqu’une configuration définie et une règle testable permettent d’autoriser certaines commandes bash sans faire confiance à toutes les commandes.

Rédigé par le modèle d'indexation à partir du texte de l'issue.