Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Feature: add a dedicated /usage command in Codex CLI [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#17190•Fetched 2026-04-10 03:44:17
View on GitHub
Comments
2
Participants
2
Timeline
7
Reactions
0
Author
stormychelstormychel
Participants
github-actions[bot]github-actions[bot]stormychelstormychel
Timeline (top)
labeled ×4commented ×2unlabeled ×1
RAW_BUFFERClick to expand / collapse

Problem

Claude Code exposes a dedicated /usage command, which makes it very discoverable to check quota / session usage from within the terminal.

Codex currently has related usage information spread across /status, rate-limit warnings, and the web usage page. There are already requests to expand /status, but there does not appear to be a dedicated issue specifically asking for a first-class /usage command.

For users switching from Claude Code to Codex, /usage is a natural command to try. Right now that expectation fails, even though the underlying need clearly exists.

Feature request

Add a dedicated /usage command in the Codex CLI / TUI.

This could be implemented as either:

  1. A standalone /usage panel focused only on usage and limits
  2. A thin alias to an enhanced usage section of /status

Either approach would be fine, but having the explicit /usage entry point matters for discoverability and parity with established CLI expectations.

Expected output

At minimum, it should show the most important limits and reset times clearly:

  • current plan / account context
  • 5-hour usage remaining, with reset time
  • weekly usage remaining, with reset time
  • whether the displayed values are live, cached, or estimated

If available, it would also help to show:

  • current model / reasoning mode that affects rate-limit consumption
  • session-level token usage or message usage
  • a short pointer to the web dashboard when the CLI cannot fetch exact values

Why this is useful

  • Improves discoverability for a common need
  • Reduces surprise when users hit limits
  • Avoids forcing users to open the browser just to inspect remaining quota
  • Matches an expectation many users already have from Claude Code

Related issues

This is adjacent to, but slightly different from, the existing request to expose fuller usage data in /status:

  • #15281

That issue is about expanding /status. This request is specifically about adding a dedicated /usage command, even if it is internally backed by the same data source.

Environment

  • Codex CLI
  • macOS
  • ChatGPT-authenticated usage / rate limits

extent analysis

TL;DR

Implement a dedicated /usage command in the Codex CLI to display quota and session usage information for improved discoverability and parity with established CLI expectations.

Guidance

  • Consider implementing the /usage command as a standalone panel or a thin alias to an enhanced usage section of /status to meet the feature request.
  • Ensure the command displays the most important limits and reset times clearly, including current plan, 5-hour usage remaining, weekly usage remaining, and whether the values are live, cached, or estimated.
  • If available, include additional information such as current model, session-level token usage, and a pointer to the web dashboard for exact values.
  • Review related issue #15281 to understand the differences between expanding /status and adding a dedicated /usage command.

Example

No specific code example is provided due to the lack of technical implementation details in the issue.

Notes

The implementation of the /usage command should prioritize discoverability, clarity, and consistency with established CLI expectations, while also considering the technical feasibility and potential impact on the existing /status command.

Recommendation

Apply a workaround by creating a feature request or proposal to implement the dedicated /usage command, as it is not currently available in the Codex CLI. This will help improve discoverability and reduce surprise for users when hitting limits.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#API routing#API middleware#SSR setup#ISR setup#authentication setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Feature: add a dedicated /usage command in Codex CLI [2 comments, 2 participants]