aws / aws/amazon-q-developer-cli

Change tool run confirmation to just Enter, vs. "y" + Enter

Offen
#861 4 Kommentare 4 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
😍 UX
Vorherrschende Sprache
Rust
Sterne
2k
Forks
439
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

### 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
- [x] I have run `q doctor` in the affected terminal session
- [x] I have run `q restart` and replicated the issue again

### Operating system

macOS 15.3.1 (24D70)

### Expected behaviour

Most tool suggestions made by Q CLI makes sense, so it'd be better if I can quickly review the suggestion and just hit the Enter key to execute the tool.

### Actual behaviour

The current behavior is that for a tool to be run, the user first needs to type "y" and then hit Enter. "y" is in the middle of the keyboard so it's a bit of a pain to hit that first and then hit Enter, especially since there could be several tool invocations in quick succession, and running the tool is the action I want to take most of the time.

The current message is:
```
Enter y to run this tool, otherwise continue chatting.
```

This could perhaps be changed to:
```
Hit Enter to run this tool, otherwise continue chatting.
```

### Steps to reproduce

_No response_

### Environment

```yaml
[q-details]
version = "1.7.1"
hash = "7d766a2d0580db62fae5a4bc2e6eb63946d4d08e"
date = "2025-03-14T22:08:03.470338Z (5d ago)"
variant = "full"

[system-info]
os = "macOS 15.3.1 (24D70)"
chip = "Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz"
total-cores = 4
memory = "16.00 GB"

[environment]
cwd = "/Users/USER/Dev/llm-cli"
cli-path = "/Users/USER/Dev/llm-cli"
os = "Mac"
shell-path = "/bin/zsh"
shell-version = "5.9"
terminal = "macOS"
install-method = "brew"

[env-vars]
PATH = "/Users/USER/Library/Python/3.9/bin:/usr/local/bin:/usr/local/sbin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Users/USER/.local/bin:/usr/local/bin:/Users/USER/.toolbox/bin"
QTERM_SESSION_ID = "35ca5b4967ab47c6bbbe4c1bf6fbfc5f"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "1.7.1"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
__CFBundleIdentifier = "com.apple.Terminal"
```

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Durchsuche den CLI-Code nach dem aktuellen Bestätigungstext und verfolge den Eingabefluss für die Tool-Genehmigung. Bestätige, dass das Drücken von Enter das vorgeschlagene Tool ausführt, während das Weiterchatten weiterhin möglich bleibt, und überprüfe die aktualisierte Eingabeaufforderung sowie das Verhalten mit den relevanten Tests.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
rust
Bereich
cli
Issue-Typ
Feature
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
35/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.