@thsottiaux nah, I think it's probably due to the translation. On my side, the double usage reads like "5 hour limit back and each week has two 5hour limit"
the new feature in Codex, Composer prediction, the "tab", is very important. It might be a key factor for the significant improvement of opus5.5.
As the accuracy of predicting what users would say to continue their dialogue increases, they could no longer need waiting for user instructions but solved them directly. Even us normal developers know to automate (using skill/hook/specific agents) some duplicate review model outcomes/continue dialogue, dealing with this thing from model/harness perspective could be much more influential.
this thing is a key to deal with the "proactive problem". cursor and claude have had such feature for a long time, this might explain how they made their recent gorgeous products. grok bot, which seems more rely on orchestration, or harness, and opus5.5, which seems tried to solve this problem model-wise.
If oai only just started caring about such features recently, I bet we could only get "better" (than opus5.5) oai models in their next generation models.
This might explain why people, like me, thought both models are powerful, but opus5.5 could do things better. they should be equivalent in most aspects, but opus5.5 wins in this and the visual quality/front-end design side.
Small features before started to show great influence today.
remember they are the people who uses unlimited Astra/GPT7 Ultra Ultra Fast. they may be never ever thought their models are both stupid and slow than opus5.5