aws / aws/amazon-q-developer-cli
to long to sart app on m2 mac
- 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.0 (25E246)
### Expected behaviour
fast and light app in my mind
### Actual behaviour
delay and long when opne kiro code and cli in macbook m2
### Steps to reproduce
_No response_
### Environment
```yaml
[q-details]
version = "1.29.7"
hash = "ed0510256130dcbdd80ab0f281d64033eda2d88e"
date = "2026-04-10T19:19:26.027865Z (17h ago)"
variant = "full"
[system-info]
os = "macOS 26.4.0 (25E246)"
chip = "Apple M2"
total-cores = 8
memory = "16.00 GB"
[environment]
cwd = "/Users/USER"
cli-path = "/Users/USER"
os = "Mac"
shell-path = "/bin/zsh"
shell-version = "5.9"
terminal = "macOS"
install-method = "unknown"
[env-vars]
PATH = "/Users/USER/.antigravity/antigravity/bin:/Users/USER/.nvm/versions/node/v25.9.0/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.local/state/fnm_multishells/28291_1775909961783/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.local/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/Users/USER/.antigravity/antigravity/bin:/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:/Library/Apple/usr/bin:/opt/homebrew/bin:/Users/USER/.cargo/bin:/Users/USER/.local/bin:/Users/USER/PROJECT/UTILS/flutter/bin:/Users/USER/Library/Android/sdk/emulator:/Users/USER/Library/Android/sdk/platform-tools:/Users/USER/.lmstudio/bin"
QTERM_SESSION_ID = "06b18e4191e241a195c65ee394526549"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "1.29.7"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
__CFBundleIdentifier = "com.apple.Terminal"
```
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia riproducendo il ritardo segnalato all’apertura di Kiro Code e della CLI su un Apple M2 Mac, utilizzando i dettagli forniti relativi a macOS, hardware e versione. Esegui q doctor e q restart come indicato, quindi individua uno scenario misurabile di ritardo all’avvio; il lavoro è completato quando il ritardo è stato riprodotto e ne sono state documentate la causa o un miglioramento verificato.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- macos, rust
- Ambito
- cli, operating-systems, performance
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Tranquilla
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 35/100