openclaw - ✅(Solved) Fix feat(openai-codex): add gpt-5.4-pro to Codex OAuth model catalog [1 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#63404Fetched 2026-04-09 07:54:09
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Participants
Timeline (top)
referenced ×2cross-referenced ×1

Root Cause

In the dist bundle, OPENAI_CODEX_XHIGH_MODEL_IDS does not include gpt-5.4-pro. The openai provider already defines it but openai-codex does not.

Fix Action

Fixed

PR fix notes

PR #63447: feat(openai-codex): add gpt-5.4-pro forward-compat #63404

Description (problem / solution / changelog)

Summary

  • Problem: ChatGPT Pro users selecting openai-codex/gpt-5.4-pro hit model not allowed: openai-codex/gpt-5.4-pro before any API call because the Codex provider did not forward-compat resolve or advertise that model (see issue #63404).
  • Why it matters: OAuth Codex users on Pro plans expect the same model id family as the API-key openai path; blocking gpt-5.4-pro breaks a primary workflow.
  • What changed:
    • extensions/openai/openai-codex-provider.ts: add gpt-5.4-pro to forward-compat resolution, XHigh/modern id lists, synthetic catalog entry, Pro pricing metadata, and preferRuntimeResolvedModel for both gpt-5.4 and gpt-5.4-pro.
    • Tests/harnesses aligned so mocks and Pi test support match real plugin behavior (model compat, thinking levels, Discord /think autocomplete mock, models list forward-compat, provider-runtime catalog expectations, e2e harness).
  • What did NOT change: Default Codex default model remains openai-codex/gpt-5.4. No change to Issue’s optional follow-up (minimum thinking tier for gpt-5.4-pro); can be tracked separately if the upstream requires non-none thinking.

Change Type (select all)

  • Bug fix
  • Feature
  • Refactor required for the fix
  • Docs
  • Security hardening
  • Chore/infra

Scope (select all touched areas)

  • Gateway / orchestration
  • Skills / tool execution
  • Auth / tokens
  • Memory / storage
  • Integrations
  • API / contracts
  • UI / DX
  • CI/CD / infra

Linked Issue/PR

Closes #63404

User-visible / Behavior Changes

  • Users can select and run openai-codex/gpt-5.4-pro when authenticated via ChatGPT/Codex OAuth without model not allowed from missing forward-compat/catalog synthesis.

Security Impact (required)

  • New permissions/capabilities? No
  • Secrets/tokens handling changed? No
  • New/changed network calls? No
  • Command/tool execution surface changed? No
  • Data access scope changed? No

Repro + Verification

Environment

  • Model/provider: openai-codex / gpt-5.4-pro (Codex OAuth, ChatGPT Pro plan as in issue).

Steps (from issue)

  1. Authenticate with openai-codex OAuth (plan Pro).
  2. Set or select model openai-codex/gpt-5.4-pro.
  3. Before: model not allowed: openai-codex/gpt-5.4-pro.
  4. After: model resolves via provider forward-compat and catalog augmentation.

Verification (local)

  • pnpm test extensions/openai/openai-codex-provider.test.ts
  • pnpm test src/agents/model-compat.test.ts -t "plugin-advertised"
  • pnpm test src/auto-reply/thinking.test.ts -t listThinkingLevels
  • pnpm test extensions/discord/src/monitor/native-command.think-autocomplete.test.ts
  • pnpm test src/plugins/provider-runtime.test.ts -t "resolves bundled catalog hooks"
  • pnpm test src/commands/models/list.list-command.forward-compat.test.ts -t "gpt-5.4-pro"

Evidence

  • Unit tests updated/added for Codex gpt-5.4-pro resolution and aligned harnesses.

Human Verification (required)

  • Verified: Static/code-path review; targeted Vitest runs above on the development branch.
  • Not verified: Live ChatGPT Pro OAuth end-to-end call (no production tokens in this environment).

Compatibility / Migration

  • Backward compatible? Yes (additive model id support).
  • Config/env changes? No.
  • Migration needed? No.

Failure Recovery (if this breaks)

  • Revert the PR commit or pin default to openai-codex/gpt-5.4 in config until fixed.

Risks and Mitigations

  • Risk: Upstream Codex API constraints (e.g. minimum thinking level) not enforced client-side.
    • Mitigation: Issue already notes optional follow-up; monitor user reports and add policy if needed.

Changed files

  • extensions/discord/src/monitor/native-command.think-autocomplete.test.ts (modified, +6/-2)
  • extensions/openai/openai-codex-provider.test.ts (modified, +93/-0)
  • extensions/openai/openai-codex-provider.ts (modified, +41/-5)
  • extensions/openai/shared.ts (modified, +10/-0)
  • src/agents/model-compat.test.ts (modified, +3/-1)
  • src/agents/pi-embedded-runner/model.provider-runtime.test-support.ts (modified, +17/-1)
  • src/auto-reply/reply.directive.directive-behavior.e2e-harness.ts (modified, +2/-0)
  • src/auto-reply/thinking.test.ts (modified, +2/-1)
  • src/commands/models/list.list-command.forward-compat.test.ts (modified, +35/-0)
  • src/plugins/provider-runtime.test-support.ts (modified, +1/-0)
  • src/plugins/provider-runtime.test.ts (modified, +1/-0)

Code Example

model not allowed: openai-codex/gpt-5.4-pro
RAW_BUFFERClick to expand / collapse

Problem

Users with a ChatGPT Pro subscription (OAuth plan: pro) cannot use openai-codex/gpt-5.4-pro through OpenClaw. The model is rejected before any API call is made:

model not allowed: openai-codex/gpt-5.4-pro

The openai-codex provider catalog only includes gpt-5.4gpt-5.4-pro is absent from the forward-compat resolution list.

Root Cause

In the dist bundle, OPENAI_CODEX_XHIGH_MODEL_IDS does not include gpt-5.4-pro. The openai provider already defines it but openai-codex does not.

Proposed Fix

Add gpt-5.4-pro to the Codex forward-compat resolution list alongside gpt-5.4.

Environment

  • OpenClaw: 2026.4.8 (9ece252)
  • OS: macOS Darwin 24.6.0 arm64
  • Auth: openai-codex OAuth, plan: pro
  • openai-codex/gpt-5.4 works fine; only gpt-5.4-pro is blocked
  • Confirmed: models.providers config override does not work for built-in providers

Notes

gpt-5.4-pro requires thinking level medium or higher (not none) — may want to handle that gracefully too.

extent analysis

TL;DR

Add gpt-5.4-pro to the OPENAI_CODEX_XHIGH_MODEL_IDS list to allow ChatGPT Pro subscribers to use the openai-codex/gpt-5.4-pro model.

Guidance

  • Verify that the openai-codex provider catalog is correctly updated with the new model ID gpt-5.4-pro.
  • Check the OPENAI_CODEX_XHIGH_MODEL_IDS list in the dist bundle to ensure it includes gpt-5.4-pro.
  • Consider adding a check for the thinking level requirement (medium or higher) for the gpt-5.4-pro model to handle it gracefully.
  • Test the fix with a ChatGPT Pro subscription and the openai-codex/gpt-5.4-pro model to ensure it works as expected.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

The fix may not apply if there are other restrictions or limitations on the openai-codex/gpt-5.4-pro model that are not mentioned in the issue.

Recommendation

Apply the workaround by adding gpt-5.4-pro to the OPENAI_CODEX_XHIGH_MODEL_IDS list, as this is a targeted fix for the specific issue described.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING