feat: extend list info with reset times.

[Carloosolrac]

🚀 Feature Request: Extend list info with reset times

Description

It would be very useful to extend the information returned by the list command to include reset times in a compact, single-line format.

Currently, the list provides useful profile-related details, but it does not indicate when certain limits or states will reset. Adding reset time information would improve transparency and usability without sacrificing readability.

Proposed Solution

Enhance the list output to include reset timestamps directly in the same row for each profile, including:

• 5-hour reset
• Weekly reset

Example

codex-profiles list

Current output:

PLUS  john.doe@gmail.com        personal   <- active
PLUS  dev.team@acmecorp.io      work

Proposed output:

PLUS  john.doe@gmail.com        personal            |  5h reset: 2026-04-05 18:00 UTC  |  week reset: 2026-04-07 00:00 UTC    <- active 
PLUS  dev.team@acmecorp.io      work                |  5h reset: 2026-04-05 20:00 UTC  |  week reset: 2026-04-07 00:00 UTC

Benefits

• Quick visibility of all relevant timing information
• Keeps output compact and CLI-friendly
• Improves usability without adding extra lines

Additional Context

A consistent format would allow for easy parsing and future extensibility if more reset types are added.

[midhunmonachan]

Thanks for the suggestion — the need makes sense, but I think this fits status better than list in its current form.

Right now list is intentionally local/lightweight, while reset times come from usage lookups. Making list fetch and render reset windows by default would make it slower, network-dependent, and a bit blurrier in scope with status.

There is also a data-model wrinkle here: it is not always just one 5-hour window and one weekly window. Some profiles can have multiple buckets/additional limits, and some profiles may not have usage data available at all.

So I do think the underlying request is valid — quick visibility of reset times is useful — but I would lean toward one of these instead:

• status --all --compact
• list --usage / list --with-status as an opt-in mode
• improving the formatting of status --all

If I implement this, I’ll probably keep list lightweight by default and add a compact usage-oriented view elsewhere.

[zorbeytorunoglu]

i actually forked this for a similar reason. a way to see all your profiles' statuses at once
it is a TUI
https://github.com/zorbeytorunoglu/codex-profiles-ui

[midhunmonachan]

@zorbeytorunoglu I like the idea, but I think some accounts are going to be too complex to represent clearly on a single line, especially when they contain multiple buckets, such as a ChatGPT Pro subscription.

For example:

I also tried this with your fork, but I could not see the full output because it gets cut off and does not seem to account for the terminal width:

Even with a TUI, I do not see a clean way to show all of this information on a single line without losing clarity or making the layout fragile.

For this repo, I do not want to spend time maintaining something where I cannot see a strong use case, especially when it would add layout complexity.

I would prefer to keep this project’s current output simple and readable. The UI-related work I am more likely to consider in the future would be things like a web UI, a quick-access OS tray icon, or similar features that add a clearer workflow benefit. I'm also considering features to build better automation around it.

That said, you are welcome to continue building this in your fork, add the features you want there, and publish it separately.

[Carloosolrac]

I tested it today and looks amazing!

[IgnisDa]

Any movement on this?