Bugs affecting legacy accounts

What version of the Codex App are you using (From “About Codex” dialog)?

Powered by Codex & OWL Version 26.924.22138
Released 26 Sept 2026

What subscription do you have?

Business Premium 5x

What platform is your computer?

Windows

What issue are you seeing?

There appears to be an account-specific Codex model entitlement discrepancy within the same ChatGPT Business workspace.

Existing OpenAI Support case: 15977381

My affected account does not show any GPT-6 models in the Codex model picker. The available models are:

• GPT-5.6 Sol
• GPT-5.6 Terra
• GPT-5.6 Luna
• GPT-5.5

A second user in the same Business workspace, using the same Codex application/version, has access to:

• GPT-6 Sol
• GPT-6 Astra
• GPT-6 Luna
• GPT-5.6 Sol
• GPT-5.6 Terra
• GPT-5.6 Luna
• GPT-5.5

I have screenshots showing both model pickers.

This makes a workspace-wide GPT-6 rollout explanation unlikely, because two members of the same workspace are receiving different effective Codex model sets.

The affected account:

• was originally created in 2022;
• was later migrated from a Personal workspace to Business in 2026;
• has a Business Premium 5x seat;
• is an Owner/Admin of the Business workspace;
• is signed into Codex using ChatGPT authentication, not an API key;
• has been fully logged out of and back into Codex without any change to the available model list.

A legacy-account migration or stale entitlement state is one possible explanation, but I cannot confirm that this is the root cause. The reproducible problem is that two users in the same Business workspace, using the same Codex client/version, receive different model entitlements.

OpenAI Support has so far inferred that this may be rollout/eligibility related, but has not provided an account-specific backend entitlement finding.

There is also a potentially related workspace provisioning inconsistency:

• the organisation shows Business Verified;
• Daybreak Blue is shown as Active;
• the workspace states that the organisation has been enabled for Daybreak Blue;
• however, the documented Models administration controls are not available in either the ChatGPT workspace admin area or the global Admin Console;
• links presented by the Daybreak UI for managing defaults/models return a 404;
• this prevents the expected Daybreak/model access configuration from being performed.

This may indicate an incomplete account/workspace migration, stale entitlement state, or inconsistent provisioning between Codex model access and newer workspace model-management controls.

Please investigate the affected account's effective Codex model entitlement and determine why it differs from another Business Premium user in the same workspace.

What steps can reproduce the bug?

1. Use Codex for Windows version 26.924.22138.
2. Sign into the affected account using ChatGPT authentication.
3. Select the Business workspace.
4. Open the Codex model picker.
5. Observe that only the following models are available:
   • GPT-5.6 Sol
   • GPT-5.6 Terra
   • GPT-5.6 Luna
   • GPT-5.5
6. Fully sign out of Codex.
7. Sign into the comparison account, which is a member of the same Business workspace.
8. Select the same Business workspace.
9. Open the Codex model picker.
10. Observe that the comparison account additionally has:
    • GPT-6 Sol
    • GPT-6 Astra
    • GPT-6 Luna
11. Sign back into the affected account.
12. Confirm that GPT-6 models remain unavailable.

The discrepancy persists after logging out and back in.

Codex Feedback ID:

no-active-thread-01a0ea1a-b957-7372-a27a-723ce597f68e

Existing OpenAI Support case:

15977381

What is the expected behavior?

Users with equivalent Business Premium entitlement and model permissions in the same Business workspace should receive the same eligible Codex model set, unless there is a documented account-specific restriction.

If GPT-6 Sol, GPT-6 Astra and GPT-6 Luna are enabled for the workspace and are available to another user in that same workspace, the affected account should also receive those models when its seat, role and permissions are equivalent.

If there is an account-specific eligibility restriction, Codex or the Admin Console should expose the effective entitlement state or reason rather than silently presenting a different model list.

Additional information

Affected account:

• ChatGPT account originally created in 2022
• Migrated from Personal to Business in 2026
• Business Premium 5x seat
• Owner/Admin
• ChatGPT-authenticated Codex session
• No API key involved
• GPT-6 is available to the affected account in ChatGPT Web, but not in Codex

Comparison account:

• Member of the same Business workspace
• Same Codex Windows client/version
• GPT-6 Sol available
• GPT-6 Astra available
• GPT-6 Luna available

Workspace / admin observations:

• Organisation is Business Verified
• Daybreak Blue is Active
• Organisation is shown as enabled for Daybreak Blue
• Models / Model Test controls are not available in the workspace admin UI
• Models / Model Test controls are not available in the global Admin Console
• Daybreak-provided admin links for model/default management return 404
• OpenAI Support has stated that workspace settings cannot make an unavailable Codex model appear

The strongest reproducible evidence is therefore:

same Business workspace + same Codex version + different user identity = different Codex model availability

This appears to be an account-specific entitlement/provisioning inconsistency rather than a normal client-side issue.