You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE]: Codex plugin improvement to remove release lag of available models #18566
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Problem
OpenCode currently relies on a hardcoded Codex model allowlist.
This means every time OpenAI releases a new Codex-compatible model, users have to wait for an OpenCode release before they can use it, even when the model is already live upstream. For instance, GPT5.4-Mini is still not available for OpenCode users unless they use a dev build.
Why this is a problem
unnecessary release lag
users cannot access newly released Codex models immediately
repeated maintenance burden for contributors and maintainers
the app becomes stale whenever OpenAI ships model updates faster than OpenCode ships releases
Suggested resolution
I think there are two good options:
allow users to explicitly add OAuth-valid Codex models within opencode.json configuration file. For example: "codex": { "additionalAllowedModels": [ "gpt5.4-mini", "gpt5.5" ] },
extend the models.dev schema with a flag indicating whether a model is valid for OAuth auth flows, so OpenCode can rely on metadata instead of a hardcoded local list
Example
A new OpenAI model can already exist in models.dev, but OpenCode will still hide/block it for Codex OAuth until the hardcoded allowlist is updated and a new release is published.
Expected outcome
New OAuth-valid Codex models should not require a new OpenCode release just to become selectable.
This issue might be a duplicate of existing issues. Please check:
OAuth filtering blocks user-configured OpenAI model aliases #13401: OAuth filtering blocks user-configured OpenAI model aliases — same root cause (hardcoded Codex OAuth allowlist preventing users from selecting valid models), with a similar proposed fix of merging user-configured model IDs into the allowlist.
codex: z.object({additionalAllowedModels: z.array(z.string()).optional().describe("Additional model IDs to allow when using Codex OAuth authentication"),}).optional().describe("Codex-specific configuration")
Activity
github-actions commentedon Mar 21, 2026
This issue might be a duplicate of existing issues. Please check:
If your request is distinct from those, feel free to clarify the difference so maintainers can track them separately.
wilkie1990 commentedon Mar 21, 2026
Proposal for option 1:
config.ts
Add new optional section to schema:
codex.ts
Import config:
Merge in any additional models from user config:
github-actions commentedon Jul 4, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.