Skip to content

Chat stops because it expects user interaction while running with --no-interactive option #1951

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
sam-amzn opened this issue May 23, 2025 · 1 comment
Open
1 task done
Labels
bug Something isn't working good first issue Good for newcomers

Comments

@sam-amzn
Copy link

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):

  • 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.

@hayemaxi
Copy link
Contributor

We can just add a system prompt for no-interactive mode to tell the model to not ask any questions or ask for confirmation.

@hayemaxi hayemaxi added bug Something isn't working good first issue Good for newcomers labels May 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants