Live data from Hacker News

Codex Resets

codex-resets.com

211–214 of 214 posts

Re: Codex Resets

#211

Earlier quoted context omitted.

The API endpoints on this page accept an OAuth token from ~/.codex/auth.json. You can simply ask Codex to create a report skill with some curl examples.

Orrrr... He could just as well click the link he has bookmarked already, and see it with his own eyes, without the token use to report on his token use.

A recursive way to burn the tokens.

Re: Codex Resets

#212
post #55

Those resets and the removal of the 5-hour usage limit are quietly anchoring me to a much higher usage baseline. I've stopped rationing and just spawn a bunch of agents to work at whatever pace I want, because there always seem to be more resets on the way (at least true for the last week). And now I am actually worried about that if one day they just stop doing so, my "normal" workflow will suddenly exceed the limit…

This guy knows what he's talking about

Re: Codex Resets

#213
post #194

Earlier quoted context omitted.

So, extend what they said to cover a 50 year timespan? "Instantaneous" wasn't mentioned or implied.

If it’s 50 years and gradual, there will be many places very close. The only “winner takes all” scenario is a sudden breakthrough when nobody else is close. Because it’s a gradient, not a binary.

If gradually one of these labs ends up with the top model that makes all the others uncompetitive, what's the difference? Why do you see time as important if the end result is the same? Winner still takes all, no?

Re: Codex Resets

#214
post #55

Those resets and the removal of the 5-hour usage limit are quietly anchoring me to a much higher usage baseline. I've stopped rationing and just spawn a bunch of agents to work at whatever pace I want, because there always seem to be more resets on the way (at least true for the last week). And now I am actually worried about that if one day they just stop doing so, my "normal" workflow will suddenly exceed the limit…

[dead]
Post reply on HN