[Bug]: Weekly usage and pace break when 5-hour limit is absent

[anthfgreco]

Existing issues

• I searched existing issues and did not find a duplicate.

What happened?

Codex currently appears to temporarily have no 5-hour usage window. The official UI only shows the weekly limit (75% remaining).

Win-CodexBar seems to assume the first usage window is always the 5-hour/session window. As a result:

• The weekly 25% used value is shown under Session
• Weekly incorrectly shows 0% used
• On-pace budget shows 0% across all periods

Expected

Usage windows should be identified by their duration/reset metadata rather than array position.

If the 5-hour window is absent, Win-CodexBar should still show the available multi-day window as Weekly, hide/mark Session unavailable, and calculate pace from the weekly quota.

Affected area

• Tray panel
• Settings UI
• Config file / settings persistence
• CLI
• Provider-specific behavior
• Installer / release packaging
• Startup / background behavior
• Other

Steps to reproduce

1. Use Codex on an account where the 5-hour usage window is not currently present.
2. Open the official Codex usage UI and confirm only the weekly limit is shown.
3. Open Win-CodexBar.
4. Observe that the weekly usage is shown as Session, Weekly shows 0%, and pace values are 0%.

Logs, screenshots, or recordings

App version

v0.47.0

Windows version

Windows 11

Additional context

No response

[Finesssee]

Thanks for the Issue, I will fix it ASAP.