Sam
21 posts


@TheRunningManZ Your tweet was the first one I saw after the second goal went in. I turned my TV off VERY calmly.
English

@papadeeley You’ve never even tweeted ever. Lol
We didn’t bother to bring on our offensive subs did we? Sat back and invited it once again
English

@kimmonismus I have a hunch that the 5 hour limit is a variable on their backend. Due to the sheer growth in users they are seeing, they have reduced the limit until they have more compute available?
English

Another reset, which is unfortunately necessary as well.
Unfortunately, it is becoming increasingly clear that the token burn rate is simply insane. I have never come close to hitting the 5-hour and weekly limits this quickly on the Pro tier as I have with 5.6 Sol. I mostly use High, not Fast Mode.
5.6 is undoubtedly better. The improvement is most noticeable in frontend work. That was where I immediately noticed that they had genuinely caught up. 5.6 also works better and remains agentic for longer. I am very satisfied overall. It is a significant step forward, if it were not for the rapid consumption.
I also still do not understand the “super app” concept. Why should I use the “Work” environment when Codex does exactly the same thing while also displaying more information? And why do I still have the classic ChatGPT app? Perhaps I missed something, but at the moment this is once again creating more confusion.
I am still hoping for resets, because otherwise this will become difficult. As for the claim that 5.6 is 54% more token-efficient, I consider that made up. It does not align with my usage at all. In fact, the opposite seems true. It feels more like 54% less token-efficient.
So, 5.6 is a good update with one major caveat.
Tibo@thsottiaux
Introducing... another usage limit reset for all our ChatGPT Work and Codex users. Should land over next 30 minutes. Hope you have an awesome weekend. Thank you for pushing our systems to the absolute limit, we have never seen traffic increase so quickly. Keep the feedback coming and we'll keep shipping.
English

@weswinder I’m not one to complain normally, but I’ve done similar work before and it definitely feels hungrier than *normal*. I guess we will wait and see how it goes.
English

@papadeeley was just checking if my backswing would be impeded (it was)
English

If you wanna know when your banked resets expire just give this to codex and it'll tell you.
read your local Codex auth token, then send a read-only GET to chatgpt.com/backend-api/wh… with Authorization: Bearer . The response includes available_count and credits[].expires_at. Do not call the consume endpoint.
English

@0xDesigner @velvet_shark I have no idea if this will work but this is a link to the shortcut I use as an app, you will have to save a codex logo for the icon yourself though.
icloud.com/shortcuts/23b8…

English

@Dimillian me too but when i ask codex abt what went wrong it always uses that as an excuse - "the thread has 676767 turns!"
English

protest how you can
just don't be silent
🥔🥔🥔@argofowl
i'm gonna shit in my hands and rub it all over my face
English

@mattiapomelli @vishalja1n Same with codex, just set it up in codex settings
English

codex app's annotate in the in-app browser is buggy and needs some love
when i select something, type a change and hit return - nothing happens
it only works with cmd+return, but then it adds the annotation as prompt reference and i have to press return again
this creates resistance when trying to iterate fast
English

@laboomemes @thsottiaux They literally just released an update so you choose when to reset yourself
English

@thsottiaux hi tibo not a q but minor quibble about your button i feel the accounting shouldnt be resetting the weeks deadline along with the reset.
for example start using june 12, reset june 14, weekly reset moves from june 19 to 21. this is one thing that feels a bit stingy compared to..
English














