Disclosure: we build Codex Reset. This is a guide to its alert channels from the people who run it, including what they can't do.
If you use Codex heavily, you have probably watched your weekly limit drop to a few percent halfway through a task. OpenAI hands out global resets from time to time, and almost all of them are announced on X by Thibault Sottiaux (@thsottiaux, usually called Tibo), who leads Codex. So the default move is to keep refreshing his profile.
Codex Reset reads those public posts for you, checks Codex Pro and Plus accounts that we own to see when a refill has actually landed, and sends the result to the channel you pick. It never touches your OpenAI account, and you don't need an account with us. Earlier posts covered how we read Tibo's posts and how our own accounts confirm that a reset has landed.
This one is practical: where you can get the alerts, how quickly each channel tends to arrive, and the small catches.
What counts as an alert
Before picking a channel, it helps to know what will reach you. The alerts menu on the site sums it up in one line: "⚠️ strong Tibo signal · ✅ verified reset · 🎟️ banked reset — resets only, nothing else."
The alerts menu on codex-reset.com, open over the homepage (screenshot, November 4, 2026).
In practice that means a handful of message types:
- ⚠️ Watch: Tibo has made a clear promise. It comes with a probability: 93% when his words give a time window, 83% when they don't.
- ⌛️: Tibo says the reset is done, and our accounts haven't confirmed it yet.
- ✅: the refill reached the Pro and Plus accounts we monitor. There is one exception, covered under limits below, and the message says when it applies.
- 🔬: our accounts measured a reset that nobody announced.
- 🎟️: a banked reset update.
A real ✅ from the public Telegram channel is headed "✅ Codex reset confirmed" and reads "Our checks show that Codex usage limits reset around 06:35 UTC on Oct 28." Times are given in UTC.
Tibo's hints and teases (👀) are not alerts. They show on the site, and our X account posts them, but Telegram, Discord, email and push stay quiet. If you only want to hear about resets, any of the main channels will do that.
Telegram
t.me/codexresetalerts is the alerts channel. Open the link and join. It's a broadcast channel, so you only receive messages.
Telegram is one of the instant channels. It carries regular resets, strong Watches and qualifying banked updates. One detail makes it calmer than it sounds: when Tibo replies to his own post with a landing time, we edit the existing ⚠️ message with the new deadline instead of sending another one. You don't get pinged twice for the same reset.
Pick Telegram if it's already open on your phone or desktop all day.
Discord
The Discord invite takes you to the Codex Reset server and drops you in #alerts. That channel carries the same alerts as Telegram, and the same in-place edit applies when a landing time arrives.
Discord fits if your team or coding community already lives there. Discord lets you turn on notifications for #alerts and mute the rest of the server, which keeps it to resets only.
Email starts at notify.codex-reset.com. Enter your address and we send a confirmation link. Opening the link doesn't subscribe you on its own. You have to press the confirm button on the page it opens.
The email subscription page at notify.codex-reset.com (screenshot, November 4, 2026).
The confirmation comes from alerts@notify.codex-reset.com. The sending domain is new, so check Spam if it doesn't show up. If it's there, marking it "not spam" helps later alerts reach your inbox.
After that you get one email for each confirmed reset, high-confidence forecast or qualifying banked-reset update. Two caveats are worth knowing:
- Email is the slowest lane. Messages go out in batches, and inbox providers add their own delay. An email can arrive minutes after the same alert is on Telegram, Discord or push.
- Delivery is at-most-once. In a rare, ambiguous failure at the email provider, you might miss one message. The system won't send a duplicate to make up for it.
The emails are transactional only: no sponsored content, affiliate placements, personalization or tracking. Each one has an unsubscribe link, and mail apps that support one-click unsubscribe will show that button too.
Email suits you if you'd rather not install anything, or you like a record you can search later. Skip it if a few minutes matter to you.
X
@codex_reset posts each alert (⚠️ ⌛️ ✅ 🎟️). It's also the one channel that posts Tibo's teases (👀), so it's a little busier than the others. The account checks the site's public data once a minute, so expect a short lag behind the instant channels.
Following the account is not enough to get notified. Turn on notifications for it in X, or the posts just wait in your timeline.
Pick X if you're on it anyway, or if you want the teases as well as the alerts.
Browser push
On codex-reset.com, open the alerts menu and turn on browser notifications. You don't need an account.
Push wakes your browser for the latest regular reset, strong Watch or banked update. If several things happen in a row, you may only see the latest state rather than every step. Old alerts never replay.
On iPhone, push only works after you add the site to your Home Screen and open it from there.
Push fits if you sit at the same computer all day and don't want another app.
Quieter options
The Atom feed. codex-reset.com/feed.xml lists Tibo's reset announcements. Each entry quotes his post and links to it on X. It's meant for feed readers and scripts. It records what he announced, not what our accounts measured, so for ✅ and 🔬 use one of the channels above.
The Tibo streams. If you want to read Tibo's posts yourself without opening X, Codex Reset · Tibo Radar on Telegram and #tibo on our Discord pass them along with little noise. They're separate from #alerts and don't mirror it. Think of them as context, not alerts.
Chinese readers can join our QQ group from the Chinese version of the site. It isn't an automatic alert channel, so pair it with one of the channels above.
Build your own alert
If none of these fit, the developer page documents a public JSON API and a read-only MCP server. In the page's words: "No key, no sign-up, no rate plan — the one condition is credit." If you show the data to other people, name the source and link it on the same surface ("Data: codex-reset.com"). A private script or a cron job that pings your own phone only needs a User-Agent that names your project.
The page's own example reads the current forecast:
curl -sS https://codex-reset.com/api/forecast \
-A 'myproject/1.0 (+https://myproject.example)' \
| jq '{p24: .probabilities.rounded_24h, p48: .probabilities.rounded_48h, last: .last_reset_at}'
If you'd rather ask your coding agent, add the MCP server. In Claude Code:
claude mcp add --transport http codex-reset https://codex-reset.com/mcp
Codex CLI and the IDE extension read ~/.codex/config.toml:
[mcp_servers.codex-reset]
url = "https://codex-reset.com/mcp"
Then ask "did Codex reset today?" between tasks. We walked through the terminal side in more detail in an earlier DEV post. The full reset history is also published as an open dataset under CC BY 4.0 on Hugging Face and Kaggle.
Which one to pick
- You want to know within minutes and Telegram is always open: Telegram.
- Your team is on Discord: Discord #alerts.
- You're at one desk all day and don't want to install anything: browser push.
- You want a searchable record and minutes don't matter: email.
- You're on X a lot, or you want the teases too: @codex_reset.
- You want it inside your own tooling: the API or MCP server.
One channel is enough. The main channels carry the same alerts, so subscribing to three just means hearing about the same reset three times.
What the alerts can't tell you
A few limits apply to every channel.
We monitor Pro and Plus. Our accounts are ChatGPT Pro and Plus. We don't cover Team or Business workspaces yet, so a ✅ tells you nothing about them.
A ✅ can rest on Tibo's word. If our monitors can't take a reading, a ✅ based on Tibo's confirmation says so in the message: "Our monitor hasn't measured it yet."
A Watch is a probability. 93% is likely, not certain. It's there to help you decide whether to wait or wrap up.
Some lanes trade detail for reliability. Email can very rarely miss a message, and push may show only the latest state. If you need every step, Telegram or Discord is the better fit.
Pick the channel you already check, and get back to work.
Codex Reset is an independent community tracker and is not affiliated with OpenAI. "Codex" is a trademark of OpenAI.
Top comments (0)