Show all Codex reset-credit expiration times, not only the next one

[simon-ami]

Problem

CodexBar currently shows only the next expiring manual Codex reset credit in the menu, e.g. Next expires in 1d.

That is useful, but incomplete when multiple reset credits are available. Users can see how many manual resets they have, but not when the other available resets expire.

Current behavior

When multiple Codex reset credits are available, the menu shows:

• Limit Reset Credits
• e.g. 2 manual resets available
• e.g. Next expires in 1d

The other available reset credits' expiration times are not visible from the menu.

Expected behavior

CodexBar should make all available reset-credit expiration times visible while keeping the default menu compact.

Preferred UI:

• Keep the current compact row unchanged by default.
• Make the Limit Reset Credits row expandable/clickable, or add a small Show details affordance.
• When expanded/clicked, show all available reset credits sorted by expiration time.

Example expanded content:

Manual reset expirations:
1. Expires in 1d — Jan 12, 14:30
2. Expires in 6d — Jan 17, 09:15
3. Expires in 13d — Jan 24, 18:00

Alternative UI:

• If it better matches existing CodexBar menu conventions, show the same information via hover/help text.
• However, click-to-expand may be preferable because hover-triggered popovers/tooltips can become noisy when moving the mouse through the menu.

The exact formatting can follow the existing reset-time display preference:

• countdown style if reset times are configured as countdowns
• absolute clock/date style if reset times are configured as absolute values
• ideally include enough date context to distinguish resets expiring on different days

Why this matters

Manual reset credits can expire independently. Showing only the next expiration helps with the most urgent one, but it does not answer:

• whether all resets expire close together,
• whether later resets can be saved safely,
• how much time remains before each individual reset expires.

This makes the reset-credit count less actionable, especially for users who have more than one available reset.

Possible implementation direction

The existing model already appears to have enough source data: the reset-credit snapshot contains the full list of credits, while the menu currently displays only the next expiring available credit.

A possible implementation path:

1. Add a model field for a full reset-credit expiration summary, e.g. codexResetCreditsDetailItems, codexResetCreditsExpandedText, or similar.

2. Build it from available, non-expired reset credits sorted by expiresAt.

3. Keep the normal menu row compact by continuing to show only the next expiration inline.

4. Show the full list only on click/expand, or as hover/help text if that fits the app better.

5. Add/extend focused tests in CodexResetCreditsMenuCardTests for:

   • multiple available reset credits,
   • sorting by expiration time,
   • excluding redeemed/expired credits,
   • respecting the reset-time display style where practical.

Suggested labels

Use these as actual GitHub labels if available; otherwise leave this section in the issue body:

• enhancement
• area:ui-ux
• provider:codex
• priority:low or priority:medium

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed June 25, 2026, 5:38 PM ET / 21:38 UTC.

Summary
Keep open: current main and v0.37.2 still render only the next expiring Codex reset credit, while the snapshot already contains the full credit list. The broader open reset-credit menu PR overlaps this request, but it also adds redemption, settings, and notifications, so maintainers still need to choose whether to land that broader path or implement this narrower UI enhancement.

Reproducibility: yes. from source inspection: the current model only exposes the next-expiring reset-credit detail and has no field for all expirations. The existing focused test also only asserts the compact next-expiry behavior.

Next step
The code path is clear, but the remaining choice is product/UI scope: narrow all-expirations detail versus folding into the broader reset-credit menu PR.

Review details

Best possible solution:

Add a narrow all-expirations summary sourced from available, unexpired Codex reset credits, or deliberately fold that UI into the broader reset-credit menu PR after maintainer scope approval.

Do we have a high-confidence way to reproduce the issue?

Yes from source inspection: the current model only exposes the next-expiring reset-credit detail and has no field for all expirations. The existing focused test also only asserts the compact next-expiry behavior.

Is this the best way to solve the issue?

Unclear until maintainers choose between a narrow hover/help or expandable summary and the broader open reset-credit menu PR that also adds redeem, settings, and notification behavior.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

• The open broader reset-credit PR may cover this request but also adds account-affecting redemption and notifications, so maintainers should decide whether this issue should ride along with that scope.
• If this is implemented as hover/help text only, accessibility and discoverability still need to expose the full all-expirations summary through the menu model or equivalent UI seam.

Codex review notes: model internal, reasoning high; reviewed against ada3660e9d61.

Label changes

Label changes:

• add clawsweeper:fix-shape-clear: Current issue advisory state selects this label.

Label justifications:

• P3: This is a low-risk UI enhancement for existing Codex reset-credit information, not an urgent broken workflow.
• impact:other: The issue affects how actionable Codex reset-credit availability is in the menu, which is meaningful UI/usage visibility impact outside the specific impact taxonomy.

Evidence reviewed

What I checked:

• Current menu model renders one expiry: The reset-credit detail helper reads only nextExpiringAvailableCredit?.expiresAt and returns a single Next expires string; there is no all-expirations projection. (Sources/CodexBar/MenuCardView+CodexResetCredits.swift:55, ada3660e9d61)
• Current view has only compact text fields: The model carries codexResetCreditsText and codexResetCreditsDetailText, and the view passes only those values into CodexResetCreditsContent. (Sources/CodexBar/MenuCardView.swift:114, ada3660e9d61)
• Source data has the full list: CodexRateLimitResetCreditsSnapshot stores credits, availableCount, and updatedAt, but its current convenience projection selects only the minimum next expiring available credit. (Sources/CodexBarCore/CreditsModels.swift:52, ada3660e9d61)
• Focused tests cover next-only behavior: The menu-card test asserts the existing single compact detail text and has no coverage for multiple available reset-credit expirations or a sorted detail summary. (Tests/CodexBarTests/CodexResetCreditsMenuCardTests.swift:42, ada3660e9d61)
• Latest release still has next-only behavior: The v0.37.2 tag points at f380287, and that release's helper also reads only nextExpiringAvailableCredit?.expiresAt. (Sources/CodexBar/MenuCardView+CodexResetCredits.swift:55, f380287041b8)
• Related open PR overlaps but is broader: The open reset-credit menu PR says it adds per-credit submenu rows, settings rows, Use Reset, and expiry notifications, and its current review status is waiting on author/maintainer follow-up. (3786c5f1988a)

Likely related people:

• steipete: Current-main blame maps the reset-credit helper and snapshot projection to the v0.37.2 release commit, and the merged reset-credit PR includes a hardening commit co-authored by this account. (role: recent area contributor and release owner; confidence: high; commits: f380287041b8, 57170e008edb, a3ea16743560; files: Sources/CodexBar/MenuCardView+CodexResetCredits.swift, Sources/CodexBarCore/CreditsModels.swift, Tests/CodexBarTests/CodexResetCreditsMenuCardTests.swift)
• rogdex24: Authored the merged PR that introduced Codex reset-credit fetching, the menu row, next-expiry detail text, and focused reset-credit tests that this issue asks to extend. (role: feature implementer; confidence: high; commits: 1ae28cfd50eb, cbd89aa02b89, 64bf84def52b; files: Sources/CodexBar/MenuCardView+CodexResetCredits.swift, Sources/CodexBarCore/Providers/Codex/CodexOAuth/CodexOAuthUsageFetcher.swift, Tests/CodexBarTests/CodexResetCreditsMenuCardTests.swift)
• brahimhamichan: Opened the broader reset-credit menu PR that appears to add per-credit expiry rows and touches the same reset-credit menu/model files. (role: adjacent follow-up contributor; confidence: medium; commits: 0d2d83995439, 3786c5f1988a; files: Sources/CodexBar/MenuCardView+CodexResetCredits.swift, Sources/CodexBar/StatusItemController+CodexResetCredits.swift, Tests/CodexBarTests/CodexResetCreditsMenuCardTests.swift)

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.