chore: add gpt-5.5 for codex plans#1605
Merged
Merged
Conversation
ChatGPT Codex CLI now lists `gpt-5.5 (current) - Frontier model for complex coding, research, and real-world work` as the headline model, and the upstream registry that this list mirrors (router-for-me/CLIProxyAPI internal/registry/models/models.json) already includes it. Without this entry AxonHub fails inbound validation with `model not found: gpt-5.5` (HTTP 422), so codex channels cannot expose the new model even when it is available on the user account.
Contributor
Greptile SummaryAdds
Confidence Score: 5/5Safe to merge — the change is a single string appended to a static list with no side-effects on existing behaviour. The only touched code is a static string slice. Adding an entry cannot break existing model lookups, routing logic, or auth flows. The new entry follows the exact same pattern as every prior model addition in this file. No files require special attention. Important Files Changed
Sequence DiagramsequenceDiagram
participant Client as Codex CLI
participant AxonHub as AxonHub Proxy
participant Registry as DefaultModels()
participant Backend as ChatGPT Codex Backend
Client->>AxonHub: POST /chat (model: gpt-5.5)
AxonHub->>Registry: Validate model ID
Note over Registry: "gpt-5.5" now present ✓
Registry-->>AxonHub: valid
AxonHub->>Backend: Forward request (gpt-5.5)
Backend-->>AxonHub: HTTP 200
AxonHub-->>Client: Response
Reviews (1): Last reviewed commit: "chore: add gpt-5.5 for codex plans" | Re-trigger Greptile |
looplj
pushed a commit
that referenced
this pull request
May 8, 2026
ChatGPT Codex CLI now lists `gpt-5.5 (current) - Frontier model for complex coding, research, and real-world work` as the headline model, and the upstream registry that this list mirrors (router-for-me/CLIProxyAPI internal/registry/models/models.json) already includes it. Without this entry AxonHub fails inbound validation with `model not found: gpt-5.5` (HTTP 422), so codex channels cannot expose the new model even when it is available on the user account. Co-authored-by: 覃康 <qinkang@robotees.tech>
looplj
pushed a commit
that referenced
this pull request
May 28, 2026
Claude Code 2.x ships claude-opus-4-7 as a first-class model, but `claudecode.DefaultModels()` still tops out at 4-6 / sonnet-4-6. As a result, channels of type `claudecode` (Claude MAX OAuth) cannot expose 4-7 via the UI's FetchModels probe — supportedModels never gets the new entry, so the orchestrator route table rejects requests with HTTP 422 `model not found: claude-opus-4-7`. Same one-line shape as #1605 (gpt-5.5 for codex) and #1006 (gpt-5.4). **Tested locally**: with this change, a Claude MAX OAuth channel whose supportedModels gets claude-opus-4-7 from FetchModels returns HTTP 200 from api.anthropic.com/v1/messages when claude code clients request claude-opus-4-7. Co-authored-by: qinkangdeid <qinkangdeid@gmail.com>
junjiangao
pushed a commit
to junjiangao/axonhub
that referenced
this pull request
May 30, 2026
Claude Code 2.x ships claude-opus-4-7 as a first-class model, but `claudecode.DefaultModels()` still tops out at 4-6 / sonnet-4-6. As a result, channels of type `claudecode` (Claude MAX OAuth) cannot expose 4-7 via the UI's FetchModels probe — supportedModels never gets the new entry, so the orchestrator route table rejects requests with HTTP 422 `model not found: claude-opus-4-7`. Same one-line shape as looplj#1605 (gpt-5.5 for codex) and looplj#1006 (gpt-5.4). **Tested locally**: with this change, a Claude MAX OAuth channel whose supportedModels gets claude-opus-4-7 from FetchModels returns HTTP 200 from api.anthropic.com/v1/messages when claude code clients request claude-opus-4-7. Co-authored-by: qinkangdeid <qinkangdeid@gmail.com>
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
2 participants
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.
ChatGPT Codex CLI now lists
gpt-5.5 (current) - Frontier model for complex coding, research, and real-world workas the headline model, and the upstream registry that this list mirrors (router-for-me/CLIProxyAPIinternal/registry/models/models.json) already includes it.Without this entry AxonHub fails inbound validation with
model not found: gpt-5.5(HTTP 422), so codex channels cannot expose the new model even when it is available on the user account.Change: one-line addition to
llm/transformer/openai/codex/constants.go'sDefaultModels(), same shape as #1006 (gpt-5.4) and #1162 (gpt-5.4-mini / gpt-5.3-codex-spark).Tested locally: with this change, a codex channel binding
claude-opus-4-7 → gpt-5.5viamodelMappingsreturns HTTP 200 from the ChatGPT Codex backend.