OpenAI Codex Client Shows Luna Reserve Fallback After Advanced-Model Limits

OpenAI’s Codex Windows client outlines a softer usage cutoff. When an eligible subscriber reaches an advanced-model limit, the app is designed to switch to an internally named reserve model with its own allowance. It then restores the user’s previous model selection when the reserve period ends. The feature, called Luna Reserve, remains behind a server-side gate.

The reserve handoff

The sequence is more than a new meter in the interface. The client is designed to preserve the model a user had selected, temporarily substitute gpt-reserve after the advanced-model allowance is exhausted, and return the original selection after Reserve ends. That structure would let Codex continue a session under a different model path without requiring the user to reset their preference.

A client-side trail

The production Windows build includes the internal model identifier gpt-reserve, a reserve_enabled feature gate, Plus and Pro account checks, and lifecycle analytics for Luna Reserve. It also contains interface text for a balance display: “Luna Reserve · {remaining}% remaining.” Together, those elements indicate a distinct product path rather than an unused model name.

The findings were drawn from Windows package 26.818.5229.0 and its embedded Codex app, version 26.818.41509, build 6962. Reported images also show GPT-Reserve in Codex’s model selector, alongside a separately metered allowance. Together, the interface and code indicate that Reserve was built to be visible to at least some enabled accounts.

Access is still server-controlled

The client does not establish that every Plus or Pro subscriber can use Luna Reserve. Its feature gate is server-controlled, and live access depends on server-side eligibility and rate-limit state. The subscription checks show the intended audience for the feature, but not its rollout size, its allowance terms, or whether access is broadly enabled.

A different kind of limit

The notable product choice is the separation between premium-model capacity and the fallback path. A user who hits an advanced-model limit would not simply encounter the same limit under a different label: the reserve model has independently tracked usage. Restoring the original model afterward keeps that fallback from becoming the user’s permanent selection.

OpenAI had not responded to a request for comment at publication time. For now, the Windows client establishes a designed reserve workflow and its eligibility controls, while the decisive question is whether OpenAI turns that workflow on for an individual account.