Skip to content

Commit b96a696

Browse files
anandgupta42claude
anandgupta42
and
claude
committed
docs: state the cold-cache model counts per artefact, not as one number
Review correctly flagged the previous note as imprecise. It said the removal leaves "only gpt-5.3-codex-spark", which is true of shipped release binaries but not of a source checkout: the committed models-snapshot.ts blob is newer than the release.yml fixture and does carry gpt-5.5. Measured against all three catalogs: release fixture (105 providers): 3 allowed -> 1 (spark) committed blob (144 providers): 4 allowed -> 2 (spark, gpt-5.5) live models.dev (207 providers): 7 allowed -> 5 (spark, 5.5, sol/luna/terra) The sequencing rationale is unchanged and holds on either reading: no pre-#1188 bundled catalog contains gpt-5.6-terra or gpt-5.6-luna, so the user loses models with no documented replacement to move to until #1188 ships. Co-Authored-By: Claude Opus 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01VqnuBDGkh1ZT65Ti7e6DHZ
1 parent 93f2616 commit b96a696

1 file changed

Lines changed: 12 additions & 5 deletions

File tree

‎packages/opencode/src/plugin/codex.ts‎

Lines changed: 12 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -121,11 +121,18 @@ const OAUTH_POLLING_SAFETY_MARGIN_MS = 3000
121121
* ``gpt-5.4-mini`` -> ``gpt-5.6-luna`` — are both already in this set, so
122122
* affected users have a working model without further change **provided their
123123
* catalog is current**. This filter only ever deletes; it cannot add a model
124-
* the catalog lacks. Release binaries built before the ``release.yml``
125-
* MODELS_DEV_API_JSON fix (#1186/#1188) embed a 2026-03-30 fixture that
126-
* contains neither replacement, so on a cold cache this removal leaves only
127-
* ``gpt-5.3-codex-spark`` selectable. That is why this change is sequenced
128-
* behind that fix rather than shipped on its own.
124+
* the catalog lacks, and NEITHER replacement is present in any pre-#1188
125+
* bundled catalog. On a cold cache this removal therefore leaves:
126+
*
127+
* - shipped release binaries (embed the 2026-03-30 ``release.yml`` fixture —
128+
* see #1186/#1188): ``gpt-5.3-codex-spark`` only, down from three.
129+
* - running from source (the committed ``models-snapshot.ts`` blob, which is
130+
* newer): ``gpt-5.3-codex-spark`` and ``gpt-5.5``, down from four.
131+
*
132+
* Either way the user loses models with no gpt-5.6 replacement to move to,
133+
* which is why this change is sequenced behind #1188 rather than shipped on its
134+
* own. Once release binaries embed a release-time catalog the replacements are
135+
* present and the gap closes.
129136
*
130137
* This is a retirement from the ChatGPT-subscription picker, NOT an API
131138
* deprecation: both ids still carry ``supported_in_api: true``, neither is on

0 commit comments

Comments
 (0)