You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow users to configure certain tools to be auto-approved for execution without requiring manual approval each time. This could be implemented through a local configuration file or as part of the MCP server configuration or the Q CLI configuration.
Actual behaviour
Currently all tool executions require manual approval in the Q CLI, which slows down workflows when using frequently-needed tools.
Steps to reproduce
User attempts to use tools repeatedly in a conversation and must approve each tool execution individually, even for trusted tools that are used frequently, and for example run in a read-only mode.
The text was updated successfully, but these errors were encountered:
I understand the security concerns, but after all the time I spent crafting a good prompt for my use case, having to approve all the tools every time I use it is so painful.
We already have functionality to achieve what you are describing:
See /tools help, as it provides ways to trust all tools or specific tools for the session. You can also start q with q chat --trust-all-tools. Finally, at the [y/n/t] confirmation prompt you can simply use t to trust that tool for the session.
Checks
Operating system
macOS 15.5.0 (24F74)
Expected behaviour
Allow users to configure certain tools to be auto-approved for execution without requiring manual approval each time. This could be implemented through a local configuration file or as part of the MCP server configuration or the Q CLI configuration.
Actual behaviour
Currently all tool executions require manual approval in the Q CLI, which slows down workflows when using frequently-needed tools.
Steps to reproduce
User attempts to use tools repeatedly in a conversation and must approve each tool execution individually, even for trusted tools that are used frequently, and for example run in a read-only mode.
The text was updated successfully, but these errors were encountered: