explaingit

qdyanbing/codex-reset-checker

Analysis updated 2026-05-18

18JavaScriptAudience · developerComplexity · 1/5Setup · easy

TLDR

A tiny CLI that reads your local Codex credential and reports how many rate limit resets are currently available.

Mindmap

mindmap
  root((repo))
    What it does
      Reads Codex auth token
      Calls reset credits API
      Prints available resets
    Tech stack
      JavaScript
      Node.js
      npx CLI
    Use cases
      Checking reset credits
      JSON output for scripts
      Custom auth file support
    Audience
      Codex users
      Developers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Check how many Codex rate limit resets are still available before starting a new session.

USE CASE 2

See the exact date each of your Codex reset credits was granted and when it expires.

USE CASE 3

Get the same rate limit reset data as JSON to feed into a script or dashboard.

What is it built with?

JavaScriptNode.js

How does it compare?

qdyanbing/codex-reset-checkerbluejacketblackhawk/saysomethingchinaran0/wujing_dic
Stars181818
LanguageJavaScriptJavaScriptJavaScript
Setup difficultyeasymoderateeasy
Complexity1/53/52/5
Audiencedevelopergeneralops devops

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

Requires an existing Codex login so ~/.codex/auth.json already has a token.

License terms are not stated in the material provided.

In plain English

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.

Copy-paste prompts

Prompt 1
Run npx codex-reset-checker and explain what each column in its output table means.
Prompt 2
Show me how to use codex-reset-checker with the --json flag and parse the output in a shell script.
Prompt 3
Explain how codex-reset-checker reads my Codex auth token without printing it.

Frequently asked questions

What is codex-reset-checker?

A tiny CLI that reads your local Codex credential and reports how many rate limit resets are currently available.

What language is codex-reset-checker written in?

Mainly JavaScript. The stack also includes JavaScript, Node.js.

What license does codex-reset-checker use?

License terms are not stated in the material provided.

How hard is codex-reset-checker to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is codex-reset-checker for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.