0.5.2: Opus 5.5, codex 0.156.1, retired models kept but refused - #39
Merged
Merged
Conversation
added 2 commits
September 23, 2026 23:54
codex-cli 0.156.1 (`codex debug models`) adds gpt-6-sol and gpt-6-luna; gpt-6-astra stays the default. claude 2.1.267 answers `fable` as claude-fable-5-1 and `haiku` as claude-haiku-4-5-20251001, and reports a 1M window for claude-opus-5. claude-opus-5-5 is rejected by 2.1.267 (`unrecognized_model`), so it is not listed. Codex verified_version moves to 0.156.1; the live codex suite passes on it apart from the two tests that need a session fixture.
claude 2.1.280 accepts claude-opus-5-5 and claude-opus-5-5[1m], both 1M, and resolves `opus` and `default` to claude-opus-5-5. verified_version moves to 2.1.280; its --help differs from 2.1.267 only in the wording of --bare and --safe-mode. The live claude suite passes on it. README: 2.1.280 accepts an unknown --effort with a stderr warning and runs at the default, and Request::effort does not validate, so that is a silent downgrade today. Recorded as a gotcha.
pathscale
force-pushed
the
fix/catalogues-codex-0.156
branch
from
September 23, 2026 17:13
4359421 to
fe96d8f
Compare
pathscale
changed the title
added 2 commits
September 24, 2026 00:30
A host stores model ids (agencyzero keeps them in its database). Deleting an entry made a stored id vanish from its picker while its runs kept using it, and some dropped ids still run: claude-fable-5 is accepted on 2.1.267 and answers as claude-opus-4-8. Model gains `retired: Option<Retired>` (since, replacement, reason). A dropped model stays in the catalogue with it set, is never the default, and discovery keeps it. A request naming one fails before anything is spawned with the new Error::RetiredModel, which carries the entry so a host can offer the replacement. Ids the catalogue does not know still pass through. Retired: claude-fable-5 (use claude-fable-5-1), codex gpt-5.4 and gpt-5.4-mini (no longer listed on 0.154.0; use gpt-6-astra). claude-haiku-4-5 is restored as a live entry: it still answers as itself on 2.1.280.
pathscale
force-pushed
the
fix/catalogues-codex-0.156
branch
from
September 23, 2026 17:30
fe96d8f to
2365cef
Compare
pathscale
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
agent-abstraction 0.5.2: Opus 5.5, codex 0.156.1 catalogue, and retired models kept but refused.
Behaviour change in a patch: a run on a retired model now fails with the new
Error::RetiredModelbefore anything spawns.Model::retired: Option<Retired { since, replacement, reason }>,Model::is_retired(). A stored id never vanishes from a host's picker. A retired entry is never the default, discovery keeps it, and a request naming it fails withError::RetiredModel, which carries the entry so the host can offer the replacement. No consumer data is touched.claude-fable-5: retired, useclaude-fable-5-1(accepted on 2.1.267 but answered byclaude-opus-4-8).gpt-5.4,gpt-5.4-mini: retired, usegpt-6-astra(no longer listed since 0.154.0).claude-haiku-4-5stays live; it answers as itself on 2.1.280.claude-opus-5-5andclaude-opus-5-5[1m], both 1M.opusanddefaultresolve to it on 2.1.280.gpt-6-solandgpt-6-luna;gpt-6-astrastays the default.fable/bestresolve toclaude-fable-5-1;claude-haiku-4-5-20251001added;claude-opus-5is 1M natively.verified_version: claude 2.1.280, codex 0.156.1.--effortwith only a warning.Verified locally with CI's exact commands:
fmt --all --check,clippy --all-targets -D warnings,test --all-targets(238 + 10 + 7 + 7),test --doc,doc --no-deps,package, the CHANGELOG-in-package check,audit. Live: claude 4/4 on 2.1.280, codex 12/14 on 0.156.1 (the two failures need the interrupt/idle session fixtures).claude-haiku-4-5was probed live and answers as itself.agency-proxy and agencyzero take
^0.5and pick this up without a manifest change. agencyzero can surfaceError::RetiredModeland flag retired entries in its picker as a follow-up.