aws / aws/amazon-q-developer-cli

`kiro-cli chat` (bun) consumes 80-130% CPU while idle

Aperta
#3,777 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub
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.4.1 (25E253)

### Expected behaviour

`kiro-cli chat` (bun process) should consume near 0% CPU when idle — i.e., when there are no active API calls, no tool executions, and no user input. An idle chat session waiting for user input should be event-driven, not busy-polling.

### Actual behaviour

The `bun` process running `kiro-cli chat` consistently consumes 80-130% CPU even when completely idle. This causes rapid battery drain on laptops.

Sampled over 6 seconds while idle:
$ for i in 1 2 3; do ps -p -o pcpu=; sleep 2; done
82.1
128.5
111.4

Running multiple `kiro-cli chat` sessions compounds the issue — observed ~220% total CPU with 4 idle sessions.

Note: Both autocomplete and inline suggestions are disabled:
- `kiro-cli settings autocomplete.disable` → true
- `kiro-cli inline status` → disabled

### Steps to reproduce

1. Open a terminal (tested with WezTerm and Tabby on macOS)
2. Run `kiro-cli chat`
3. Do nothing — leave it idle
4. Check CPU usage: `ps -Arco pid,pcpu,comm | grep bun`
5. Observe bun process at 80-130% CPU continuously

### Environment

```yaml

[q-details]
version = "2.0.1"
hash = "4a41569da83e25b6ab94898d7c4c83fa18cb5216"
date = "2026-04-17T02:21:00.156808Z (7d ago)"
variant = "full"

[system-info]
os = "macOS 26.4.1 (25E253)"
chip = "Apple M4"
total-cores = 10
memory = "16.00 GB"

[environment]
cwd = "/Users/USER/playground"
cli-path = "/Users/USER/playground"
os = "Mac"
shell-path = "/bin/zsh"
shell-version = "5.9"
terminal = "Wezterm"
install-method = "unknown"

[env-vars]
PATH = "/Users/USER/.local/bin:/Users/USER/.toolbox/bin:/opt/homebrew/opt/python@3.13/libexec/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:/opt/pkg/env/active/bin:/opt/pmk/env/global/bin"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
__CFBundleIdentifier = "com.github.wez.wezterm"
```

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

Inizia riproducendo il problema con `kiro-cli chat` su macOS e profilando il processo `bun` inattivo. Esamina il percorso dell’input inattivo e dell’event loop per identificare l’origine dell’attività continua della CPU. Il lavoro è completato quando una sessione inattiva consuma quasi lo 0% di CPU con il completamento automatico e i suggerimenti inline disabilitati, mentre le chiamate attive e l’esecuzione degli strumenti continuano a funzionare.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
bun, macos
Ambito
cli, performance
Tipo di issue
Bug
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Tranquilla
Chiarezza
Abbastanza chiara
Idoneità per principianti
52/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.