aws / aws/amazon-q-developer-cli
keyboard entry slows down incredibly in iTerm2 when running q chat
- Lingua principale
- Rust
- Stelle
- 2k
- Fork
- 439
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
### 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 26.0.0 (25A353)
### Expected behaviour
Quick response time. When I quit out of Q chat -- things return to normal.
### Actual behaviour
The keyboard is incredibly slow when I type. It take a second or more to press each key.
### Steps to reproduce
run q chat
keyboard in iTerm2 slows down significantly
### Environment
```yaml
[q-details]
version = "1.15.0"
hash = "eb8db5c635fc469f3bd94ead16bb4bfb32d7443b"
date = "2025-09-02T17:57:24.662205Z (11d ago)"
variant = "full"
[system-info]
os = "macOS 26.0.0 (25A353)"
chip = "Apple M4 Pro"
total-cores = 14
memory = "24.00 GB"
[environment]
cwd = "/Users/USER/Code"
cli-path = "/Users/USER/Code"
os = "Mac"
shell-path = "/bin/zsh"
shell-version = "5.9"
terminal = "iTerm 2"
install-method = "brew"
[env-vars]
PATH = "/Library/Java/JavaVirtualMachines/temurin-17.jdk/Contents/Home/bin:/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/bin:/opt/homebrew/opt/python@3.12/libexec/bin:/opt/homebrew/bin:/Library/Java/JavaVirtualMachines/temurin-17.jdk/Contents/Home/bin:/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/bin:/opt/homebrew/opt/python@3.12/libexec/bin:/opt/homebrew/bin:/Users/USER/.nvm/versions/node/v24.4.1/bin:/Users/USER/.local/share/zinit/polaris/bin:/Library/Java/JavaVirtualMachines/temurin-17.jdk/Contents/Home/bin:/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/bin:/opt/homebrew/opt/python@3.12/libexec/bin:/opt/homebrew/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/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:/Library/Apple/usr/bin:/Users/USER/.cargo/bin:/Applications/iTerm.app/Contents/Resources/utilities:/Users/USER/.local/bin:/Users/USER/Library/Application Support/JetBrains/Toolbox/scripts"
QTERM_SESSION_ID = "e43c05b2bd9a4f539a469028dddcf3c5"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "1.15.0"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
__CFBundleIdentifier = "com.googlecode.iterm2"
```
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia riproducendo `q chat` in iTerm2 su macOS 26 con l’ambiente riportato, quindi esegui `q doctor` e `q restart` come descritto. Confronta la reattività della tastiera prima, durante e dopo la chat; è completato quando la digitazione rimane reattiva mentre `q chat` è in esecuzione e torna alla normalità quando termina.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- macos, rust, shell
- Ambito
- cli, operating-systems, performance
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 30/100