Socket path: "/var/folders/2p/32l4qnk15kg__pfjynhqdb_40000gn/T/kirorun/t/1b2113b1a7dd472d9784e6576e4745d4.sock

### 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.7.2 (24G313)

### Expected behaviour

Socket path: "/var/folders/2p/32l4qnk15kg__pfjynhqdb_40000gn/T/kirorun/t/1b2113b1a7dd472d9784e6576e4745d4.sock

### Actual behaviour

The cli coding agent froze and shut down. I believe it may be the apple coding assistant just quit

### Steps to reproduce

I have a multi dev pipeline (5 at least that I am surely aware of due to the buildout of an AGI level ecosystem. Nodableowrld.

### Environment

```yaml

[q-details]
version = "1.20.0"
hash = "ac0d8dec437123a79962295fdad4122ef9642da3"
date = "2025-11-16T23:27:14.134786Z (2d ago)"
variant = "full"

[system-info]
os = "macOS 15.7.2 (24G313)"
chip = "Apple M4"
total-cores = 10
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 = "/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:/Users/USER/.local/bin"
QTERM_SESSION_ID = "1b2113b1a7dd472d9784e6576e4745d4"
Q_SET_PARENT_CHECK = "1"
Q_SHELL = "/bin/zsh"
Q_TERM = "1.20.0"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
__CFBundleIdentifier = "com.apple.Terminal"
```

Il report non indica alcun file sorgente, test o punto di ingresso affidabile per la riproduzione. Inizia esaminando i percorsi socket e shutdown macOS della CLI e riproduci il blocco, se possibile; per considerare il lavoro completato è necessario identificare il problema e aggiungere un test di regressione o un’altra correzione verificata.

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