[Bug] Claude model intermittently becomes unavailable within the same session
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 35/100
Direzione di ricerca
Start by reproducing the failure in Kiro CLI and Kiro IDE using the listed Claude models, then run q doctor and q restart as reported. Compare the successful and failed requests using the provided request IDs and determine where model availability or routing is handled; done means identifying and resolving the intermittent same-session failure.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Checks
- I have searched github.com/aws/amazon-q-developer-cli/issues and there are no duplicates of my issue
- I have run
q doctorin the affected terminal session - I have run
q restartand replicated the issue again
Operating system
macOS 26.5.2 (25F84)
Expected behaviour
Claude Opus works successfully in the same Kiro IDE/CLI session,
but a few seconds later the next request fails with:
"The model 'claude-opus-x' is not available."
No model switch, logout, region change, or client restart occurred.
This happens intermittently in both Kiro IDE and Kiro CLI.
This does not look like a permanent entitlement or region issue,
because the same model succeeds immediately before failing.
Actual behaviour
The selected Claude model intermittently becomes unavailable during the same active session.
For example, Claude Opus works normally for one request and returns a valid response. Then, only a few seconds later, without changing the model, account, region, configuration, or restarting the client, the next request fails with:
The model 'claude-opus-4.8' is not available.
I have also observed the same behavior with claude-opus-5 in Kiro CLI.
The issue is intermittent: the model may become available again later without any configuration changes.
This happens in both Kiro IDE and Kiro CLI, so it appears to be related to model availability/routing rather than a local client configuration issue.
Screenshots are attached showing a successful Claude request followed immediately by a "model not available" error in the same session.
Example request IDs:
- 6273cb42-7dec-4a24-95f1-394c55bdbbea
- cf554955-134b-4c29-86ce-cd26a6bc68b7
- 36c6f7fa-c53b-48ad-8437-df54409a55d6
Steps to reproduce
-
Open Kiro IDE or Kiro CLI.
-
Select a Claude model, for example
claude-opus-4.8orclaude-opus-5. -
Send a prompt and confirm that the model responds successfully.
-
Continue using the same session and the same model.
-
Send another prompt a few seconds or minutes later.
-
Intermittently, the request fails with:
The model 'claude-opus-x' is not available.
-
Retry later without changing any configuration, and the same model may work again.
The issue is not consistently reproducible on every request, but occurs frequently enough to interrupt normal usage.
Environment
<This will be visible to anyone. Do not include personal or sensitive information>
[q-details]
version = "2.24.0"
hash = "240642df93e76b55141520bb767a757f4434d006"
date = "2026-09-23T20:12:52.807706Z (2d ago)"
variant = "full"
[system-info]
os = "macOS 26.5.2 (25F84)"
chip = "Apple M5"
total-cores = 10
memory = "16.00 GB"
[environment]
cwd = "/Users/USER/laya-patpat-lab"
cli-path = "/Users/USER/laya-patpat-lab"
os = "Mac"
shell-path = "/bin/zsh"
shell-version = "5.9"
terminal = "Wezterm"
install-method = "unknown"
[env-vars]
PATH = "/Users/USER/.local/bin:/opt/homebrew/opt/mysql-client/bin:/opt/miniconda3/bin:/opt/miniconda3/condabin:/opt/homebrew/bin:/opt/homebrew/sbin:/Users/USER/.local/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:/pkg/env/global/bin:/Library/Apple/usr/bin"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
__CFBundleIdentifier = "com.github.wez.wezterm"
- Lingua principale
- Rust
- Stelle
- 2k
- Fork
- 439
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di aws/amazon-q-developer-cli
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
aws/amazon-q-developer-cli#3898 ·
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 90/100
aws/amazon-q-developer-cli#3851 ·
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 72/100
aws/amazon-q-developer-cli#3316 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
aws/amazon-q-developer-cli#3023 · 2 commenti ·
-
Support for T3 Code terminalAperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 55/100
aws/amazon-q-developer-cli#3917 · 1 commento ·
Tutte le issue di aws/amazon-q-developer-cli
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 92/100
bytecodealliance/wasmtime#14433 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
I maintainer di solito rispondono entro 1 giorno