tibo-reset-codex

Verifies ChatGPT and Codex usage-limit reset events by cross-checking announcements, trackers, and local account data.

1.4k|216|Updated Oct 22, 2025
One-click install
npx skills add https://github.com/daymade/claude-code-skills --skill tibo-reset-codex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tibo-reset-codex
Source: https://github.com/daymade/claude-code-skills/tree/main/tibo-reset-codex
Command: npx skills add https://github.com/daymade/claude-code-skills --skill tibo-reset-codex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Users of ChatGPT and Codex often cannot tell whether their usage quota was actually reset, when the next reset lands, or whether an unannounced platform-wide reset occurred. This Skill distinguishes four reset types (official Tibo announcements, silent platform resets, banked credit resets, and per-account weekly cycles) and produces a single evidence-backed conclusion instead of ambiguous guesses.

Core Features & Use Cases

  • Announcement tracking: Queries the Tibo Radar timeline API, fxtwitter mirrors, and OpenAI status pages to find official reset announcements and incident-driven compensations, with fallback channels when endpoints fail.
  • Local forensic analysis: Parses ~/.codex rollout session snapshots to reconstruct weekly quota curves, pinpoint reset intervals to minute-level ranges, and detect silent resets or window reconfigurations.
  • Evidence-graded conclusions: Classifies findings by scope (single account, cross-account observation, large-scale silent reset, or officially confirmed global reset) and converts Pacific Time announcements to Beijing time.
  • Use Case: A user says their Codex weekly quota suddenly returned to 100% but no tracker shows a reset. The Skill checks local rollout snapshots, searches concurrent user reports, and concludes whether a silent platform reset occurred.

Quick Start

Ask the assistant when my Codex usage limit resets and whether a silent reset already happened today.

Frequently Asked Questions about tibo-reset-codex

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check when my Codex usage limit resets?

Check the ChatGPT product usage page or Codex CLI /status for your account's Next reset time, which is authoritative for per-account weekly cycles. Local ~/.codex rollout snapshots also record resets_at timestamps for the weekly and 5-hour windows.

How to verify a silent Codex quota reset without an official announcement?

Confirm your own account returned to 100% and that the change cannot be explained by your normal reset schedule, then search for concurrent first-hand reports from other accounts. Multiple independent accounts resetting ahead of schedule supports a large-scale silent reset conclusion.

What is a Tibo reset and who announces it?

A Tibo reset is a broad usage-limit reset announced by Thibault Sottiaux, OpenAI's Codex/ChatGPT Work lead, on X as @thsottiaux. These resets have no fixed schedule and typically accompany user milestones or incident compensation.

Does the Tibo Radar tracker confirm that a reset has landed?

No. The Radar API's reset_verification_status field only has pending, rejected, or null values and never flips to a landed state. Actual arrival must be confirmed through follow-up announcement posts or in-product balance checks.

Why does my quota show reset but trackers show nothing?

Trackers only index public announcements, not backend account state, so silent platform resets and limit-configuration switches leave no tracker entries. Your product usage page or local rollout snapshots are higher-grade evidence than an empty aggregator result.

How do I convert Tibo's Pacific Time announcements to Beijing time?

Use the OS timezone database with TZ=America/Los_Angeles and TZ=Asia/Shanghai rather than fixed offsets, since Pacific observes daylight saving from March to November. PDT 14:00 converts to 05:00 Beijing the next day; PST adds one more hour.