›_ Codex Issues
Codex Issues / #30222

Feature request: support 12-hour time in the Usage remaining panel

Open 💬 2 comments Opened Jun 26, 2026 by Sultanimate
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Summary

Please let the Codex desktop app show times in the Usage remaining panel in 12-hour format, or at least follow the user's locale / OS clock preference.

Current behavior

The Usage remaining panel shows the reset time in 24-hour / military time. Example: 18:49.

Expected behavior

One of these would solve it:

  • Respect the user's locale / OS time format automatically
  • Respect Codex locale settings when formatting usage reset times
  • Add an explicit app setting for 12-hour vs 24-hour time

Repro

  1. Open the Codex desktop app on Windows.
  2. Open the profile / usage panel.
  3. Look at the time shown next to the usage reset information.
  4. The time appears in 24-hour format.

Environment

  • Codex Windows app
  • App version: 26.623.4041.0
  • Locale override in Codex config: en-US
  • Windows short time format: 12-hour (h:mm tt)

Notes

Even with en-US configured in Codex and Windows already set to a 12-hour clock, the usage panel still displays 24-hour time. It would be preferable if this part of the UI matched the rest of the user's regional formatting expectations.

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 2 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #28419

Powered by Codex Action

Nicolas0315 · 2 months ago

I pushed a candidate fix here:
https://github.com/openai/codex/compare/main...Nicolas0315:codex/usage-reset-12-hour?expand=1

Summary:

  • The TUI reset timestamp now reads the Windows short-time pattern via LOCALE_STIMEFORMAT and uses a 12-hour label when the OS preference is 12-hour.
  • Non-Windows behavior remains 24-hour.
  • The formatter keeps existing default snapshot behavior stable, with focused coverage for 12-hour labels, next-day suffixes, midnight/noon, and Windows time-pattern parsing.

Verification:

  • Local rtx4090 Windows: just fmt; git diff --check; cargo test --manifest-path codex-rs\Cargo.toml -p codex-tui reset_timestamp_ -- --nocapture; cargo test --manifest-path codex-rs\Cargo.toml -p codex-tui detects_hour_cycle_from_windows_time_patterns -- --nocapture; cargo check --manifest-path codex-rs\Cargo.toml -p codex-tui.
  • SSH cyberagent-mac-m5max: fetched 230a7d17e; git diff --check; same focused tests; cargo check --manifest-path codex-rs/Cargo.toml -p codex-tui.
  • SSH nicolas2025: fetched 230a7d17e; git diff --check; cargo check --manifest-path codex-rs\Cargo.toml -p codex-tui.
  • SSH nicolas-macbook-pro: fetched 230a7d17e; git diff --check; Rust toolchain unavailable, so cargo checks skipped there.
  • SSH rtx5060ti: fetched 230a7d17e; git diff --check; cargo check is blocked by that host's linker setup (link.exe rejects MSVC flags, cargo exit 101); confirmed no lingering cargo/rustc/link processes.
  • Latest origin/main: git merge-tree --write-tree origin/main HEAD reports no conflicts.