@jun_song That’s not the case at all, do you ever look at the comments of these guys statuses? Look at how many people beg for the ability to buy resets
Weekly usage limit shows 80% remaining, but any attempt to chat in Codex says I’ve reached my usage limit. Fully updated. Rebooted. @thsottiaux what’s the deal? @OpenAI
@theright_agenda@BertZZ_@Southside_Gunn The problem with people like you is that you expect someone else to argue you down to this reality, and that they should be willing to and nice about it. Why can’t you figure that shit out for yourself?
@kelvinbuildss It’s tough to say. When the resets stop coming every other day or every day, it’s gonna be a different story. Codex 5.6 on $100 plan is still not all that much cheaper efficiency wise than most of my workflows with Claude max 5.
Any other codex users getting a ton of model capacity errors today? Have been happening since ~6am and have made most of the morning workflows unusable @OpenAI
@thsottiaux Allowing the user to set what percentage dip in usage triggers a pause pop-up notification would be even more ideal. It brings visibility, but allows the user to stay in a good workflow.
@thsottiaux Even if difficult, I don’t think a hard five hour limit is the answer. Notification set every 10% dip inusage or some other non-inhibiting option would make more sense. The only beneficial instance is sub Agent runaway, but offering a pause at every 10% dip would solve for this
Already automated several aspects of my finances, recipe management, and unlocked a three week long barrier I had with Claude Code. GPT-5.6 Sol really feels like the next big shift.
@thsottiaux@gabrielchua Better up-to-date understanding of model plugin availability. It was easy to manage when there were many, but now with new ones each day, it can be difficult to understand what that serves any given function, and model awareness as they become available would be awesome