Skip to content

Feature request: Auto-approve specific tools in Q CLI #1938

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 task done
bdeak opened this issue May 22, 2025 · 2 comments
Open
1 task done

Feature request: Auto-approve specific tools in Q CLI #1938

bdeak opened this issue May 22, 2025 · 2 comments

Comments

@bdeak
Copy link

bdeak commented May 22, 2025

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.

@fsmiamoto
Copy link

This is currently my biggest pain point with Q.

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.

@hayemaxi
Copy link
Contributor

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.

Are you proposing something else?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants