feat(sse): restore GPT-6 Astra effort aliases and Codex 0.153.4 pin - #13026
Merged
diegosouzapw merged 6 commits intoSep 11, 2026
Merged
diegosouzapw merged 6 commits into
diegosouzapw merged 6 commits into
Conversation
HouMinXi
added a commit
to HouMinXi/OmniRoute
that referenced
this pull request
Sep 8, 2026
…gments Signed-off-by: Minxi Hou <houminxi@gmail.com>
|
Would like to have GPT 6 Astra in v3.8.51. And hope it released soon @diegosouzapw :) |
HouMinXi
added a commit
to HouMinXi/OmniRoute
that referenced
this pull request
Sep 10, 2026
…gments Signed-off-by: Minxi Hou <houminxi@gmail.com>
HouMinXi
force-pushed
the
feat/codex-astra-pin-fonts
branch
from
September 10, 2026 11:22
357db61 to
f351559
Compare
HouMinXi
added a commit
to HouMinXi/OmniRoute
that referenced
this pull request
Sep 10, 2026
…gments Signed-off-by: Minxi Hou <houminxi@gmail.com>
HouMinXi
force-pushed
the
feat/codex-astra-pin-fonts
branch
from
September 10, 2026 13:02
f351559 to
8745a21
Compare
…odels.json Signed-off-by: Minxi Hou <houminxi@gmail.com>
Signed-off-by: Minxi Hou <houminxi@gmail.com>
Astra needs one more max-effort row. Drop the four-line comment so the file does not grow past the freeze. Signed-off-by: Minxi Hou <houminxi@gmail.com>
…onts Signed-off-by: Minxi Hou <houminxi@gmail.com>
…gments Signed-off-by: Minxi Hou <houminxi@gmail.com>
HouMinXi
force-pushed
the
feat/codex-astra-pin-fonts
branch
from
September 11, 2026 08:31
8745a21 to
a509b21
Compare
Contributor
Author
|
CI red on this PR matches current Measured on tip
Unique diff does not touch those files. Contributor-only; not merging. |
diegosouzapw
merged commit Sep 11, 2026
d92bc8e
into
diegosouzapw:release/v3.8.51
8 of 16 checks passed
This was referenced Sep 15, 2026
Githab-capibara
added a commit
to Githab-capibara/OmniRoute
that referenced
this pull request
Sep 17, 2026
…iegosouzapw#13026) Three related things that genuinely belong together: the registry and suffix splitter not knowing Astra while the live catalog serves it, the Codex client pin Astra requires, and dropping `next/font/google` so a production image build does not reach fonts.googleapis.com. --- Validated in one consolidated worktree cut from `release/v3.8.51`, boarded with the other 19 PRs of this batch. Two in-batch conflicts, both additive and resolved by keeping each side: the `ENVIRONMENT.md` table (diegosouzapw#13035 + diegosouzapw#13011) and the `chatHelpers.ts` import block (diegosouzapw#12975 on the tip + diegosouzapw#13017). - `typecheck:core` clean; `check:dashboard-typecheck` OK (206 pre-existing, within baseline); `check:changelog-integrity` OK; `check:docs-counts` migrations ✓ - complexity 2816 / baseline 3218 and cognitive-complexity 1271 / baseline 1437 — both under baseline - 531 of 532 focused assertions green across the batch's 46 test files - `check-file-size` rebaselined for the batch's real growth (annotation `_rebaseline_2026_09_11_mergebatch_v3851_houminxi`, landed on diegosouzapw#13038), attributed per PR The single red is **not this batch**: `tests/unit/combo/quota-weighted-strategy.test.ts` → "A/B isolation: 7 hard-empty + 2 at 0.5% + 1 at 40%, floor=1" asserts an order between two connections of identical weight and flakes on the pure tip too — 2 failures in 4 runs at `origin/release/v3.8.51` with nothing from this batch applied.⚠️ base-red inherited: diegosouzapw#12732 — `Docs Gates`, `Merge integrity`, `No new ESLint warnings`, `Unit Tests fast-path` and `Fast Quality Gates` reproduce on the pure tip (provider count 356 vs the 358 the modules define, SKILL.md drift, and `open-sse/utils/stream.ts` at 3115 > frozen 3098, untouched here). Thanks @HouMinXi — the live evidence on these (X500 logs, `storage.sqlite` state, real `/v1/models` probes, the 36-minute outage write-up) is what let a 20-PR batch be reviewed as a unit.
QuangBlue
pushed a commit
to QuangBlue/OmniRoute
that referenced
this pull request
Sep 24, 2026
CODEX_NATIVE_UNPREFIXED_MODELS lists the Codex model ids that should reach the ChatGPT subscription when a client sends them without a provider prefix (diegosouzapw#9275), bounded to installs with an active Codex connection (diegosouzapw#9447). GPT-6 Astra came to the Codex catalog in diegosouzapw#13026 with the same effort tiers as gpt-5.6-sol/terra, but its ids were never added to the set. With both a Codex and an OpenAI connection active: - bare `gpt-5.6-sol` routed to Codex, bare `gpt-6-astra` routed to OpenAI; - /v1/models listed bare `gpt-5.6-*` ids but no bare `gpt-6-astra*` id. Add gpt-6-astra and its six effort variants. The diegosouzapw#9447 bound still applies: OpenAI's catalog also lists `gpt-6-astra`, so without an active Codex connection the bare id keeps resolving to OpenAI. The effort variants are Codex-family ids (codex and codex-app-server); they already routed to Codex when it was active, so for them only the /v1/models rows change, exactly as for the gpt-5.6 variants. Test: tests/unit/codex-gpt6-astra-bare-id.test.ts (3 of 4 cases fail on the previous model.ts; the fourth pins the no-Codex fallback). Three comments in models-catalog-low-noise-flag.test.ts counted the set's size ("26 of the 27") and one cited its old line range; they now describe the one exception without a count and point at the file only.
muhamadgalihsaputra
pushed a commit
to niyatna/NiyatnaRoute
that referenced
this pull request
Sep 27, 2026
…iegosouzapw#13026) Three related things that genuinely belong together: the registry and suffix splitter not knowing Astra while the live catalog serves it, the Codex client pin Astra requires, and dropping `next/font/google` so a production image build does not reach fonts.googleapis.com. --- Validated in one consolidated worktree cut from `release/v3.8.51`, boarded with the other 19 PRs of this batch. Two in-batch conflicts, both additive and resolved by keeping each side: the `ENVIRONMENT.md` table (diegosouzapw#13035 + diegosouzapw#13011) and the `chatHelpers.ts` import block (diegosouzapw#12975 on the tip + diegosouzapw#13017). - `typecheck:core` clean; `check:dashboard-typecheck` OK (206 pre-existing, within baseline); `check:changelog-integrity` OK; `check:docs-counts` migrations ✓ - complexity 2816 / baseline 3218 and cognitive-complexity 1271 / baseline 1437 — both under baseline - 531 of 532 focused assertions green across the batch's 46 test files - `check-file-size` rebaselined for the batch's real growth (annotation `_rebaseline_2026_09_11_mergebatch_v3851_houminxi`, landed on diegosouzapw#13038), attributed per PR The single red is **not this batch**: `tests/unit/combo/quota-weighted-strategy.test.ts` → "A/B isolation: 7 hard-empty + 2 at 0.5% + 1 at 40%, floor=1" asserts an order between two connections of identical weight and flakes on the pure tip too — 2 failures in 4 runs at `origin/release/v3.8.51` with nothing from this batch applied.⚠️ base-red inherited: diegosouzapw#12732 — `Docs Gates`, `Merge integrity`, `No new ESLint warnings`, `Unit Tests fast-path` and `Fast Quality Gates` reproduce on the pure tip (provider count 356 vs the 358 the modules define, SKILL.md drift, and `open-sse/utils/stream.ts` at 3115 > frozen 3098, untouched here). Thanks @HouMinXi — the live evidence on these (X500 logs, `storage.sqlite` state, real `/v1/models` probes, the 36-minute outage write-up) is what let a 20-PR batch be reviewed as a unit.
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
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.
Summary
Codex's live catalog still lists
gpt-6-astra, but the static registry and suffix splitter did not. Catalog clients that pickcodex/gpt-6-astra-high(and the other effort aliases) gotbad_request. GPT-5.6 Sol/Terra/Luna already had those aliases in the registry; Astra did not.This PR:
-lowthrough-ultra) to the Codex and OpenAI registries, and teachessplitCodexReasoningSuffixthose aliases.@openai/codex@0.153.4in the Dockerfile andDEFAULT_CODEX_CLIENT_VERSIONin lockstep. Astra rejects older Codex client versions.src/app/layout.tsxfrom loading Inter vianext/font/google, so a production image build does not need fonts.googleapis.com.Overlap: #12759 also lands Astra. This branch is the three live-unique commits from our 2026-09-06 image that the 2026-09-08 recut dropped, rebased onto current
release/v3.8.51.Test plan
tests/unit/codex-astra.test.tsand the Codex / OpenAI catalog tests (84/84)npm run typecheck:corenode scripts/check/check-file-size.mjs --base-ref fcc2dcd1a(Codex executor comment shrunk so the freeze does not grow)After merge / in a deploy image:
GET /api/v1/modelslistscodex/gpt-6-astra-highandcodex/gpt-6-astra-max. A pin of those ids must not 400not available in the active live catalog.