Check for Unused Codex Reset Credits Across Multiple ChatGPT Accounts via OpenClaw

If you're running Codex through OpenClaw on more than one ChatGPT account, check for banked rate-limit reset credits before they expire. One user found that a second OAuth account had a reset credit expiring in two days — but unless you're logged into the app as that account, you can't see it.

Scan All Accounts

Have your agent check both (or all) OAuth codex accounts. In this case, the scan found four unused credits on the hidden account and two on the visible one. Redeeming the soonest-expiring credit cleared the cooldown within a minute, bringing Codex back on that account.

Critical Implementation Details

• Undocumented endpoint: The reset endpoint isn't documented anywhere. Don't tell your agent to find or create a script — it will guess wrong. Point it at github.com/aaamosh/codex-reset and openai/codex PR #28154 instead. Both are real and already proven.
• Skill discovery failure: Even after building a skill to trigger the reset automatically, it didn't fire — because the skill file was missing its frontmatter, and the agent's own skill discovery never saw it. After setup, explicitly list the agent's skills and confirm the new one is present.
• One-shot redemption: A successful HTTP 200 response means the credit is consumed. Gate the call behind an explicit user confirmation (yes), and never retry a call that already returned 200.

Who This Is For

Developers running multiple ChatGPT OAuth accounts through OpenClaw for Codex access, especially those hitting rate limits and relying on reset credits.