Skip to content

v0.1.7 — model-unavailable failure type

Choose a tag to compare

View all tags
@zhjai zhjai released this 01 Jun 12:41
· 9 commits to main since this release
v0.1.7
a4bf22b

Reported from real use: specifying gpt-5.2-codex was rejected by the Codex account; re-running with the default model succeeded.

  • Add model-unavailable to the failure taxonomy (Preflight runbook + Arena Limitations template). It is distinct from auth (authentication is fine) and refusal (the model declined to answer).
  • Guidance: don't pin a specific model version unless the account is confirmed to support it; prefer the default model. The standard retry for model-unavailable is to drop the override and re-run with the default model.

This is exactly the v0.1.5 Failure-type / Retry-recommendation mechanism working in the field — the report used that format and the one-variable-change retry succeeded; v0.1.7 just fills the taxonomy gap.

Assets 2
Loading