@xKaka1456 I choose 2 and 5. We shouldn’t assume that compute capacity can be freed up or expanded. Options 1, 3, and 4 all violate this fundamental constraint.
@thsottiaux@maria_rcks I still believe in ChatGPT and its ability to deliver newer, more powerful models. Today’s challenges are only temporary. What matters most is never losing the drive to innovate and explore the frontiers of AI. Keep pushing forward, We believe in you!
@thsottiaux Of all the updates over these 9 days, this is the one I’m most eager to test! Since Day 7’s context update, I keep getting “stream disconnected before completion” errors in Codex chats and have to restart the app to recover. Please fix this!
@thsottiaux Tibo, I suggest OpenAI follow Anthropic: offer more granular model tiers with matching subscription and API pricing. Let users choose compute based on their needs instead of treating everyone the same. This could improve resource allocation and ease OpenAI’s compute constraints.
@thsottiaux My Codex threw errors 4–5 times today, which has never happened to me before. I suspect this may be related to recent official changes to the context window. I had previously manually increased mine to 828K tokens.
@thsottiaux I need uninterrupted workdays. A 5-hour cap would disrupt my workflow, even with 2x weekly limits, leaving unused weekend capacity. Keep the no-window model and consider flexible rate limits or optional background queues. You previously ruled out restoring the cap.
@thsottiaux We enjoy freedom from 5-hour limits, not watching the clock. As a Pro $200 user, I’ve accepted lower quotas, but 5-hour caps would disrupt my work. I don’t want extra accounts for weekdays, then waste quota or sacrifice my weekends.