@thsottiaux @OpenAI @OpenAIDevs Here’s exactly what happened with my Codex resets today: I used a saved banked reset around 2pm so I could keep working. My plan was to use that allowance over the next few days, then continue when my regular weekly reset arrived. In the evening, after doing some work, I checked my usage. I had about 92% remaining, and the app still showed my next automatic reset in 3 days. This was after I had already used the banked reset. Then the global reset happened following Tibo’s announcement. My allowance went from 92% to 100%, but my next automatic reset moved from 3 days away to 7 days away. So the global reset gave me an 8-percentage-point top-up, while the renewal I was planning around moved four days further out. Meanwhile, my saved banked reset was already spent. Had I known this was coming, I could have kept it for later. I plan actual work around the allowance and reset dates your app shows. Changing those dates on a whim messes with my schedule. Calling it a global reset doesn’t address what happens to people who just used their saved reset. Please give back my banked reset and restore the reset date shown before the global reset.

Google already scans apps before they reach the Play Store. But too many false alarms and minor warnings teach developers to tune out these emails. Use Argon in that loop to find and verify real flaws in the app’s Firebase setup, then help fix them before users download it.