OpenAI Codex Product Head Tibo issued an update to Astra users, stating that the team has verified recent quality feedback with some users, confirmed and fixed multiple defects, and announced a usage reset before midnight local time today.

Old model skills were reported to trigger too frequently. Tibo stated that some skills written for previous models would intervene too often or block the model's self-checking, leading to deviations during task progression and missing self-checks. The team has completed repairs for this triggering path, aiming to return skill calls to a verifiable state rather than forcing old workflows into the new model.

An optional context management experiment has been closed. This experiment may have caused premature stopping of writing or allowed the model to respond to older messages from the current session. Tibo provided a rough estimate: about 4,000 to 5,000 users were affected by this experiment. The experiment was opt-in but has been withdrawn from online pathways and will no longer be a default or optional diversion.

Misconfigured engines have been removed. Tibo stated that some engines were incorrectly configured, causing measurable quality degradation in the long-tail traffic flowing through these engines. The issue did not manifest as a total crash but was concentrated in tail requests: the completion, follow-up consistency, and result verification of the same type of tasks were significantly worse on the wrong engines. The related engines have now been taken offline.

The team has also made several smaller changes. Tibo listed three sensory goals: more consistent follow-up execution, more accurate tracking of the user's latest message, and more complete checks of intermediate results during task progression. He also mentioned that publicly posted failure examples by users and those who directly assisted in troubleshooting were key inputs for quickly locating the issues.

From a market mechanism perspective, this is an event-driven quota replenishment rather than a regular billing cycle rollover. On the buy side are heavy users who have paid and are consuming Astra/Codex quotas; the reset is equivalent to re-adding tokens wasted due to defects back into their accounts. There is no public secondary market clearing on the sell side, and the pressure falls on OpenAI's own computing power and quota pool. Beneficiaries are paid users affected by skill misfires, context experiments, and faulty engines; the burden falls on the product and infrastructure teams that need to complete routing switches, engine takedowns, and full resets before the midnight window. Funds do not leave the platform but are redistributed once between "paid subscriptions - actual usable computing power."

Public interactions show that this update post received about 12,700 likes, around 1,900 replies, and approximately 910,000 views, with a third-party reset tracking site in the community marking it as a high-certainty signal within the midnight window. Tibo also mentioned around the same time that GPT-5.3-Codex-Spark will be retired next week due to declining usage and the availability of stronger models, which is part of the product closure during the Astra transition period.

Source: Public Information