Opaque error when login expires

Checks

• I have searched github.com/aws/amazon-q-developer-cli/issues and there are no duplicates of my issue
• I have run q doctor in the affected terminal session
• I have run q restart and replicated the issue again

Operating system

macOS 15.7.1 (24G231)

Expected behaviour

When the login expires in the middle of a session, Q CLI should inform me that I should login again

Actual behaviour

Instead, Q CLI responds with an opaque error:

Amazon Q is having trouble responding right now:
   0: Failed to send the request: dispatch failure (other): No token
   1: dispatch failure (other): No token
   2: dispatch failure
   3: other
   4: No token

Location:
   crates/chat-cli/src/cli/chat/mod.rs:1024

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

Steps to reproduce

No response

Environment

<This will be visible to anyone. Do not include personal or sensitive information>

[q-details]
version = "1.18.1"
hash = "5610605baef17b76ef41448f2e943f021c2b2273"
date = "2025-10-13T22:31:07.064465Z (2d ago)"

[system-info]
os = "macOS 15.7.1 (24G231)"
chip = "Apple M3 Pro"
total-cores = 12
memory = "36.00 GB"

[environment]
cwd = "/Users/USER"
cli-path = "/Users/USER"
install-method = "unknown"

[env-vars]
PATH = "/Users/USER/.local/share/mise/installs/node/22.20.0/bin:/Users/USER/.local/share/mise/installs/python/3.12.6/bin:/Users/USER/.local/share/mise/installs/python/3.11.10/bin:/Users/USER/.local/share/mise/installs/python/3.10.15/bin:/Users/USER/.local/share/mise/installs/python/3.9.20/bin:/Users/USER/.local/share/mise/installs/python/3.8.20/bin:/Users/USER/.config/smithy-mcp/mcp-servers:/opt/homebrew/bin:/opt/homebrew/sbin:/opt/homebrew/opt/node@18/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:/Users/USER/.cargo/bin:/Applications/iTerm.app/Contents/Resources/utilities:/Users/USER/.local/bin:/Users/USER/Library/Application Support/JetBrains/Toolbox/scripts:/Applications/Visual Studio Code.app/Contents/Resources/app/bin:/Users/USER/.toolbox/bin"
QTERM_SESSION_ID = "5e27b50199084ffe9da3dffbc0ac4ba1"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "1.17.1"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
__CFBundleIdentifier = "com.googlecode.iterm2"

Beginne bei crates/chat-cli/src/cli/chat/mod.rs:1024 und verfolge, wie das fehlende Token gemeldet wird, nachdem die Anmeldung einer Sitzung abgelaufen ist. Reproduziere das Problem mit q doctor und q restart in der betroffenen Terminalsitzung und überprüfe anschließend, dass der Benutzer aufgefordert wird, sich erneut anzumelden, statt den undurchsichtigen Fehler „No token“ zu sehen.