No More Waiting When Codex Quota Runs Out: Hermes Adds /usage Reset

For developers who live in Codex, the most frustrating moment is not a wrong answer—it is hitting the quota wall halfway through a long task and having to wait or switch tools to keep going. The context is already built, tool calls have run, and now you need to break the flow to redeem a reset elsewhere.

Hermes Agent just merged PR #64280, adding the /usage reset command. Now you can redeem banked Codex usage-limit resets directly from Hermes, without opening the Codex CLI or the website, and without losing your session.

What problem this solves

OpenAI gives ChatGPT-plan Codex users rate-limit reset credits. Think of them as emergency top-ups: when you hit the 5-hour or weekly usage cap, spending one banked credit refills the entire allowance.

Until now, redeeming those credits required one of:

  • The Codex CLI
  • The Codex desktop app
  • The OpenAI web dashboard

For developers who use Hermes as their main entry point, that meant an extra context switch. /usage reset wires the same redemption flow into the tool you are already using.

Core usage: three steps to refill

1. Update Hermes

hermes update

2. Make sure your ChatGPT account is logged in

hermes auth

You need a ChatGPT-plan account that includes Codex access.

3. Check your current usage

/usage

If you have banked resets, Hermes will now show something like:

You have 2 resets banked - use /usage reset to activate

4. Reset your quota

/usage reset

If one of the rate-limit windows is fully exhausted, Hermes will redeem one banked credit and restore the full 5-hour plus weekly allowance.

hero

Force reset and the guardrails

The command is more careful than it first appears. A single banked reset restores the entire 5-hour and weekly quota, so using it early is wasteful.

Hermes therefore refuses to redeem unless at least one rate-limit window is fully exhausted, and it tells you how much of the busiest window is still left. Override with --force:

/usage reset --force

Possible outcomes:

Outcome Meaning
reset Redemption succeeded, quota restored
nothing_to_reset No window was fully exhausted, credit was not spent
no_credit No banked resets available
already_redeemed This credit was already redeemed (idempotent UUID guard)
reset_wrong_provider Current provider is not openai-codex

Why this matters for developers

Two kinds of interruption hurt the most while coding:

  1. Flow interruption — you are deep in a complex refactor and the model stops responding.
  2. Context interruption — Codex has already read the project, run commands, and produced intermediate files; switching tools means re-establishing all of that state.

/usage reset keeps the reset action inside the same chat interface you are already using. It is especially useful for:

  • Long refactoring sessions — the task has been running for hundreds of lines and then hits the cap.
  • Multi-file analysis — the project context is already loaded; switching tools would mean re-explaining the task.
  • Cron or background jobs — an unattended run that hits the quota can fail entirely; a reset command provides a recovery path.
  • Tight debug loops — frequent Codex calls burn through quota faster; manual resets save a lot of waiting.

How it works under the hood

According to PR #64280, the implementation is clean and follows the official Codex client semantics:

  • Reuses Hermes’ existing three-tier Codex credential resolver.
  • Calls OpenAI’s /rate-limit-reset-credits/consume endpoint with a UUID idempotency key, matching the official Codex client.
  • Handles PathStyle differences (/wham vs /api/codex) and the ChatGPT-Account-Id header.
  • Available on both CLI and Gateway, so it works from the terminal and from messaging platforms like Telegram or Discord.
  • New i18n keys added across all 16 locales, and docs updated in cli.md and the messaging index.

The test coverage is also thorough: unit tests, gateway command tests, i18n parity tests, and a real-socket E2E against a local fake Codex backend that verified hint rendering, the guard block, --force redemption, the idempotency key on the wire, and both CLI entry points.

Another daily update from the “workhorse” team

If you watch the Hermes commit log, you know this project ships almost every day. PR #64280 was merged two days ago, while the repository already had commits from four, seven, and nineteen hours ago. The Nous Research team’s maintenance cadence is the kind of “workhorse” rhythm that makes Hermes feel reliably alive.

/usage reset is not a flashy headline feature. It is a small, practical improvement that fixes a real pain point for people who actually use Hermes to get work done. Those are often the best kinds of updates.

Key takeaways

  • /usage reset lets you redeem Codex banked resets directly inside Hermes, no need to jump to the Codex CLI or website.
  • Run hermes update, confirm hermes auth, then use /usage reset when needed.
  • It protects you from wasting credits by default; only fully exhausted windows trigger a reset. Use --force to override.
  • Outcomes include reset, nothing_to_reset, no_credit, already_redeemed, and reset_wrong_provider.
  • Works on both CLI and Gateway, so terminal and chat-platform users can use it.

References: