{"slug": "is-a-codex-usage-limit-reset-coming-check-from-your-terminal-with-a-free-api-or", "title": "Is a Codex usage-limit reset coming? Check from your terminal with a free API (or MCP)", "summary": "A developer built codex-reset.com, a free, keyless service that tracks OpenAI Codex usage-limit reset announcements and publishes a 24/48-hour probability forecast as JSON and a read-only MCP server. The API exposes a forecast endpoint, a dated timeline of confirmed resets with source links, and Codex surface status history, and can be added to Codex or Claude Code via an MCP URL with no install or account.", "body_md": "If you use OpenAI Codex a lot, you've probably hit the weekly limit and asked the same question everyone asks: *is a reset coming, or should I just wait it out?*\n\nThere are two different kinds of \"reset\", and people mix them up:\n\n`/status` inside Codex shows when yours rolls over. Nobody else can predict it for you.\nThis post is about the second kind. [codex-reset.com](https://codex-reset.com/) tracks those announcements, keeps a dated record with source links, and publishes a probability that another one lands in the next 24 or 48 hours. All of it is available as **free JSON with no API key**, and as an **MCP server** you can plug into Codex itself. Below is how to use both from a terminal.\n\nDisclosure: this account belongs to the project. Everything below is free to use; the only condition is a visible credit if you show the data to other people.\n\n```\ncurl -sS https://codex-reset.com/api/forecast \\\n  -A 'my-script/1.0 (+https://example.com)' \\\n  | jq '{p24: .probabilities.rounded_24h, p48: .probabilities.rounded_48h, confidence, last: .last_reset_at}'\n{\n  \"p24\": 20,\n  \"p48\": 35,\n  \"confidence\": \"low\",\n  \"last\": \"2026-09-12T08:09:17.000Z\"\n}\n```\n\nThat's a percentage chance of a global reset within 24h and 48h, how confident the model is, and when the last confirmed reset happened. It's a forecast, not a promise: treat 20% as \"probably not today\".\n\nThe `-A` header matters. Server-side readers are asked to send a `User-Agent` that names the project, so the site can tell real integrations from anonymous scrapers.\n\nEvery entry in the record links to the original post:\n\n```\ncurl -sS https://codex-reset.com/api/timeline \\\n  -A 'my-script/1.0 (+https://example.com)' \\\n  | jq -r '[.events[] | select(.group == \"reset\" and .announcement_state == \"announced\")]\n           | sort_by(.announced_at) | reverse | .[0:3][]\n           | \"\\(.announced_at)  \\(.url)\"'\n2026-09-12T08:09:17.000Z  https://x.com/thsottiaux/status/2098685367058612394\n2026-09-08T01:34:00.000Z  https://x.com/thsottiaux/status/2097043464538264003\n2026-08-31T02:34:27.000Z  https://x.com/thsottiaux/status/2094252447271366730\n```\n\nThe `announcement_state == \"announced\"` filter matters. A post that only *promises* a reset shows up in the record too, but a reset only counts once it's actually announced. That's the same rule the site's ✅ alerts use.\n\nWhen Codex starts failing, check whether it's an outage before you blame your quota:\n\n```\ncurl -sS https://codex-reset.com/api/status-history \\\n  -A 'my-script/1.0 (+https://example.com)' \\\n  | jq -r '.current.surfaces[] | \"\\(.label): \\(.status)\"'\nCodex Web: operational\nCodex API: operational\nCodex CLI: operational\nVS Code extension: operational\nCodex in ChatGPT Desktop: operational\n```\n\nThe same data is exposed as a read-only MCP server over Streamable HTTP. There's nothing to install, no key, and no account. Add it to `~/.codex/config.toml`:\n\n```\n[mcp_servers.codex-reset]\nurl = \"https://codex-reset.com/mcp\"\n```\n\nOr in Claude Code:\n\n```\nclaude mcp add --transport http codex-reset https://codex-reset.com/mcp\n```\n\nThen just ask, in the agent:\n\nThere are three tools, `get_reset_forecast`, `get_reset_timeline` and `get_codex_status`, all read-only. Config for Cursor, VS Code and others is in the [codex-reset-mcp repo](https://github.com/suvadadepolo-blip/codex-reset-mcp). The repo also installs as a Codex plugin.\n\nThe record only changes when a reset is announced, so a watcher just compares `last_reset_at`:\n\n``` bash\n#!/usr/bin/env bash\n# Poll politely: the data refreshes about once a minute; every 5 minutes is plenty.\nUA='reset-watch/1.0 (+https://example.com)'\nlast=\"\"\nwhile true; do\n  now=$(curl -sS -A \"$UA\" https://codex-reset.com/api/forecast | jq -r '.last_reset_at')\n  if [ -n \"$last\" ] && [ \"$now\" != \"$last\" ]; then\n    osascript -e 'display notification \"Codex limits were reset\" with title \"Codex\"' 2>/dev/null \\\n      || notify-send \"Codex limits were reset\" 2>/dev/null \\\n      || echo \"Codex limits were reset at $now\"\n  fi\n  last=$now\n  sleep 300\ndone\n```\n\nIf you'd rather not run anything, the site also pushes the same event to Telegram, Discord and browser notifications.\n\nThe API is free and keyless, with CORS open. The terms fit in one line: if you show the data to people, credit it where it appears (`Data: codex-reset.com`, linked), and send an identifying `User-Agent` from servers. Field reference and polling guidance: [codex-reset.com/developers](https://codex-reset.com/developers).\n\nSeveral open-source menu-bar apps and bots already read it this way. If you build something on it, I'd like to hear about it in the comments.", "url": "https://wpnews.pro/news/is-a-codex-usage-limit-reset-coming-check-from-your-terminal-with-a-free-api-or", "canonical_source": "https://dev.to/codexreset/is-a-codex-usage-limit-reset-coming-check-from-your-terminal-with-a-free-api-or-mcp-3enb", "published_at": "2026-09-24 02:24:07+00:00", "updated_at": "2026-09-24 02:59:25.164109+00:00", "lang": "en", "topics": ["ai-tools", "ai-agents", "agent-protocols", "developer-tools", "ai-products"], "entities": ["OpenAI", "Codex", "codex-reset.com", "Claude Code", "Cursor", "VS Code", "ChatGPT", "GitHub"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/is-a-codex-usage-limit-reset-coming-check-from-your-terminal-with-a-free-api-or", "markdown": "https://wpnews.pro/news/is-a-codex-usage-limit-reset-coming-check-from-your-terminal-with-a-free-api-or.md", "text": "https://wpnews.pro/news/is-a-codex-usage-limit-reset-coming-check-from-your-terminal-with-a-free-api-or.txt", "jsonld": "https://wpnews.pro/news/is-a-codex-usage-limit-reset-coming-check-from-your-terminal-with-a-free-api-or.jsonld"}}