Make usage limits easier to access during active Codex sessions

What variant of Codex are you using?

App 26.623.42026

What feature would you like to see?

Type

Feature request / UX enhancement

Summary

It would be very helpful to make Codex usage information easier to access while working in an active conversation.

Currently, usage information is placed under the profile area. To check it, the user has to open the profile bar, move to the usage button, and click it before the usage details are shown. This feels too hidden for something that developers often need to check during active work.

Problem

During development, users do not only need to monitor the conversation context. They also need to understand whether their remaining usage is enough for the current task to continue, especially for limits such as 5-hour usage and weekly usage.

This is a frequent action while working with Codex, particularly when:

• A task is long-running
• A session is using a large amount of context
• The user is deciding whether to continue in the current session
• The user is planning how much work to delegate to Codex
• The user wants to avoid hitting limits in the middle of an important task

Because the usage view is currently hidden behind the profile menu, checking it repeatedly during development feels unnecessarily cumbersome.

Proposed solution

Expose usage information in a more accessible location during active Codex sessions.

Possible approaches:

• Add a usage indicator near the composer or session status area
• Add usage to the same area where context usage is shown
• Add a quick-access usage button in the sidebar
• Add a /usage command
• Show a compact usage popover when hovering or clicking a usage indicator

The UI does not need to show all details all the time. Even a compact indicator with quick access to the full usage panel would significantly improve the workflow.

Expected behavior

Users should be able to check their current usage state with one quick action while staying in the conversation context.

Ideally, Codex should make it easy to see both:

• Current session/context usage
• Account-level usage limits, such as 5-hour and weekly availability

Why this matters

For developers, usage is part of task planning. When working on a complex feature or a long debugging session, knowing whether there is enough remaining usage affects how the user continues the work.

Making usage easier to access would reduce friction and help users make better decisions during active development.

Additional context

The current profile-menu location is reasonable for account settings, but usage is more operational than static account information. It behaves more like runtime status, so it would be useful to surface it closer to the active session UI.

Additional information

_No response_