aws / aws/amazon-q-developer-cli

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

Open
#1,951 2 comments 0 reactions 0 assignees View on GitHub
bug good first issue
Dominant language
Rust
Stars
2k
Forks
439
PR merge metrics
No merged PRs in 30d

Description

### Checks

- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue

### 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> 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 ""` where prompt can be any requests to do some code changes.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.