For higher-priced ChatGPT Pro plans, it would be great to have a small vacation/rollover feature for Codex.
If a user does not use Codex for a week, that weekly capacity currently expires even though no compute was used.
A simple solution could be to allow users to bank one unused weekly reset, with an expiration date and a maximum of one stored reset.
This would make expensive Codex plans more flexible without allowing unlimited accumulation of compute.
This is kind of already a thing, no?
Here I’ve got 3 banked resets - I used one up last week as Codexometer reminded me I had one about to expire (so no brainer to use it) … and Tibo kindly gave us one yesterday:
(you don’t need codexometer to have or use these, I’m just using its “resets dashboard” to present the example)
Thanks! I meant something slightly different: automatically banking unused weekly capacity. For example, if I don’t use Codex for a week because I’m on vacation, one weekly reset could roll over instead of expiring. The current banked resets seem to be promotional grants from OpenAI rather than rollover of unused subscription capacity.
Right. I think that would be unusual in the world of SaaS but never say never …
