qdyanbing/codex-reset-checker — explained in plain English
Analysis updated 2026-05-18
Check how many Codex rate limit resets are still available before starting a new session.
See the exact date each of your Codex reset credits was granted and when it expires.
Get the same rate limit reset data as JSON to feed into a script or dashboard.
| qdyanbing/codex-reset-checker | bluejacketblackhawk/saysomething | chinaran0/wujing_dic | |
|---|---|---|---|
| Stars | 18 | 18 | 18 |
| Language | JavaScript | JavaScript | JavaScript |
| Setup difficulty | easy | moderate | easy |
| Complexity | 1/5 | 3/5 | 2/5 |
| Audience | developer | general | ops devops |
Figures from each repo's GitHub metadata at analysis time.
Requires an existing Codex login so ~/.codex/auth.json already has a token.
codex-reset-checker is a small command line tool with no external dependencies that checks how many rate limit resets are currently available for OpenAI's Codex tool. It works by reading the access token already stored locally in a file at ~/.codex/auth.json, the same credential Codex itself saves after you log in, and using it to call an internal ChatGPT backend endpoint that reports reset credits. The tool only prints information about the reset credits themselves: how many are available, each one's status, its title, when it was granted, and when it expires. It explicitly does not print the access token, any refresh token, cookies, or other identifying information, so running it should not expose your login credentials in the terminal output. The simplest way to use it is running npx codex-reset-checker directly, which prints a small table showing the count of available resets along with the status, expiry date, grant date, and title of each one, using your local timezone by default. From a local checkout of the project, the same command can be run as npx . A few flags extend this basic usage. Passing --json switches the output to machine readable JSON instead of the table. Passing --timezone lets you choose a specific timezone for the displayed dates rather than relying on the system default. Passing --auth-file lets you point the tool at a different credentials file if your Codex login is stored somewhere other than the default location. If the underlying API responds with a 401 error, the tool reports plainly that the credential has expired or that the authorization header was rejected, rather than failing with an unclear error.
A tiny CLI that reads your local Codex credential and reports how many rate limit resets are currently available.
Mainly JavaScript. The stack also includes JavaScript, Node.js.
License terms are not stated in the material provided.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.