@reach_vb: Hola! quick usage update on usage patterns for Sol: We’ve shipped several improvements that should make typical Sol usa…

X AI KOLs Following Products

Summary

Sol, an AI assistant for ChatGPT Work and Codex, receives improvements for longer usage and efficiency, with a reset of usage limits and a return of the five-hour limit.

Hola! quick usage update on usage patterns for Sol: We’ve shipped several improvements that should make typical Sol usage last ~18% longer, with significantly larger gains for some power users. The five-hour limit will also return tomorrow. The reason: Sol works longer, calls more tools and pushes harder - even at the same reasoning effort. That makes it much better at difficult tasks, but some tool-heavy workflows were consuming far more usage than intended. We’ve improved this, especially around tool waits and large web searches, and will keep making Sol more efficient. We’ve reset usage limits for everyone on ChatGPT Work and Codex. Thank you for pushing Sol hard and helping us improve it!
Original Article
View Cached Full Text

Cached at: 07/30/26, 05:58 PM

Hola! quick usage update on usage patterns for Sol:

We’ve shipped several improvements that should make typical Sol usage last ~18% longer, with significantly larger gains for some power users. The five-hour limit will also return tomorrow.

The reason: Sol works longer, calls more tools and pushes harder - even at the same reasoning effort. That makes it much better at difficult tasks, but some tool-heavy workflows were consuming far more usage than intended.

We’ve improved this, especially around tool waits and large web searches, and will keep making Sol more efficient.

We’ve reset usage limits for everyone on ChatGPT Work and Codex.

Thank you for pushing Sol hard and helping us improve it!

Tibo (@thsottiaux): Hello people of Sol! I’ve reset usage limits for all ChatGPT Work and Codex users. Together with that, a quick update on GPT-5.6 Sol usage limits.

Over the past few weeks, many of you have told us that Sol was using your Codex limits faster than expected. To be clear, we have

Similar Articles