I would like to provide some feedback regarding the recent Pro experience, reset eligibility, referral limits, and ongoing Codex issues.
I upgraded to Pro on June 16 and paid the same $100 subscription fee as other Pro users.
On June 17, OpenAI issued a global reset. However, users who subscribed before the eligibility cutoff appeared to receive both the automatic refresh and an additional manual reset, while I only received the automatic refresh.
Because my subscription was only one day old, the automatic refresh provided almost no practical benefit to me. My limits were already fresh. As a result, users paying the same subscription price ended up receiving different amounts of usable reset capacity.
I would appreciate clarification on whether this difference was intentional, a grandfathered benefit for earlier subscribers, or simply the result of eligibility timing.
I am also confused by the referral system.
Referral opportunities appear to be limited to three total attempts. If an invitation is sent to someone who is not eligible or is not recognized as a qualifying new user, the referral slot can still be consumed.
This design feels counterproductive. Instead of encouraging users to invite real friends, it creates an incentive to search for guaranteed qualifying accounts in order to avoid wasting referral opportunities.
In addition, Codex is still affected by the TRACE logging issue. Even after updating to the latest version, excessive TRACE logs can continue to generate large amounts of disk activity and consume system resources. This has been one of the most disruptive issues I have encountered while using Codex.
Taken individually, each of these issues may have an explanation. However, when combined, they have left me feeling that newer Pro subscribers are receiving a significantly worse experience than earlier subscribers despite paying the same subscription fee.
I am not asking for special treatment.
I am simply asking for transparency regarding the reset policy, clarification regarding referral-slot consumption, and information about the status of the TRACE logging issue.
Thank you for your time and consideration.