When Codex says "midnight PST," what time is that on your desk?

When a Codex usage-limit reset shows up on X, the time string is usually not in your timezone.

It says things like “by midnight PST,” “before 10am PST,” or “landing by EOD.” That is fine if everyone on the team lives in California. It is less fine if one person is in Shanghai, another in Berlin, and someone else is reading the same screenshot six hours late.

This is not a /status walkthrough. Your personal 5-hour and weekly windows still live in the Codex UI. This is about the other clock: public reset announcements that teams try to plan around — and how easy those clocks are to misread.

The announcement is Pacific. Your calendar is not.

OpenAI-side Codex reset notes from Tibo often use Pacific labels: PST, “midnight,” “EOD,” “around 2pm.” Those are useful hints. They are not a world clock.

A few conversion habits that cut most of the pain:

1. Anchor to UTC first. Convert the Pacific time to a single UTC instant, then to each teammate’s local zone. Arguing in three local times at once is how “we thought it was already live” starts.
2. Treat “PST” as ambiguous until proven otherwise. Literal PST is UTC−8. Pacific local time in summer is often PDT (UTC−7). History of these announcements shows both readings show up in the wild — and they differ by one hour. One hour is enough to miss a reset window you were waiting on.
3. “EOD” is not a timestamp. End of day in Pacific can mean several different hours depending on who said it. Prefer a confirmation post (“all propagated,” “done”) over an EOD forecast when you need to know it landed.

If you work from China Standard Time (UTC+8), “10am PST” is not a morning event. Literal PST puts that near 02:00 the next calendar day in Beijing; a PDT reading shifts it by another hour. Remote teams that sync on Slack screenshots without naming the zone will disagree about whether the reset “should have happened already.”

Personal reset ≠ public reset

Two clocks get mashed together in Discord and Twitter threads:

• Your account windows — 5-hour / weekly (and whatever else your plan shows). Check them in Codex (/status or Settings → Usage). Nobody else’s screenshot is your number.
• Public / global-style resets — announced or confirmed for eligible paid users in public posts. Those are events. They are not proof that your bar moved until you verify in-product.

Banked resets are a third mechanism again: stored credit you choose to use, not the same thing as “everyone’s weekly just refilled.” Mixing those three under the word “reset” is how threads talk past each other.

One shared board beats five private conversions

The failure mode is familiar: someone pastes a Pacific time, three people convert it differently, and the channel argues about who is “right” while the useful question — has the public confirmation landed, and against which source post? — goes unanswered.

For that public clock, a small curated page helps more than another CLI one-liner. Codex Reset Watch keeps confirmed and upcoming Codex usage-limit resets on a live UTC countdown, with the original Tibo source posts, timezone notes, a verified history, and browser alerts when a new reset (or a usage-limit rule change) is confirmed on the site. It is unofficial and free to open — it does not log into your account, and the times it shows are public confirmation or observation anchors, not a claim about OpenAI’s exact backend second.

Use it as the team’s shared “has it landed?” board. Keep /status for your remaining percentage.

A short checklist before you schedule around a reset post

• Does the post name a timezone, or only a city-less “tonight”?
• Is it a forecast (“landing by…”) or a confirmation (“propagated,” “done”)?
• Are you converting literal PST or Pacific local (PDT) — and did the whole team pick the same one?
• Are you talking about a public reset, your rolling windows, or a banked card?

Get those four straight and most timezone fights disappear. The remaining work is boring on purpose: one UTC reference, one source link, one check in your own Codex UI.