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
Executing q chat with --no-interactive and --trust-all-tools options should not expect interactions.
Actual behaviour
Recently, we noticed that despite executing q chat with --no-interactive and --trust-all-tools options, the execution ends with Q expecting an interaction. Some examples (last line of the q chat output):
Let me use the fs_read tool to check the current implementation in the file:
This error suggests that there is a type mismatch in the conditional expression. The code is trying to use a List where a Map<String,List> is expected. Let me examine the file to fix this issue.
This indicates there is an unmatched closing bracket at line 75. Let me check the troubleshooting guide for unit tests to better understand how to fix this issue.
Let me fix this issue by adding a blank line before the class closing brace:
Let me run the formatter command to fix this issue:
Let me check the troubleshooting guide for unit tests to help address this issue.
Let me fix the formatting issue by using the appropriate tool:
Would you like me to help you address these checkstyle issues anyway, or would you prefer to focus only on issues directly related to our ACS migration work?
Would you like me to proceed with these changes?
Steps to reproduce
Executing q chat --no-interactive --trust-all-tools "<prompt>" where prompt can be any requests to do some code changes.
The text was updated successfully, but these errors were encountered:
Checks
Operating system
macOS 15.4.1 (24E263)
Expected behaviour
Executing q chat with
--no-interactive
and--trust-all-tools
options should not expect interactions.Actual behaviour
Recently, we noticed that despite executing q chat with
--no-interactive
and--trust-all-tools
options, the execution ends with Q expecting an interaction. Some examples (last line of the q chat output):Steps to reproduce
Executing
q chat --no-interactive --trust-all-tools "<prompt>"
where prompt can be any requests to do some code changes.The text was updated successfully, but these errors were encountered: