What version of Codex is running?
No response
Which model were you using?
No response
What platform is your computer?
No response
What steps can reproduce the bug?
Overview
The recently merged rate limits display (Tui: Rate limits #3977) has several UX and accessibility issues that make it difficult to read and understand.
Issues Identified
1. Confusing tip text
Current: Tip: run `/limits` right after Codex replies for freshest numbers
Issue: Awkward phrasing and unclear grammar make this hard to parse quickly
Suggestion: Tip: Run `/limits` after Codex responses for the most current usage data.
2. Poor visual chart design
Issue: The ASCII chart using repeated (>_) logos creates excessive visual noise that makes it difficult to quickly assess usage patterns
Suggestion: Consider simpler characters like █ ▓ ░ or even just # . for better readability
3. Low contrast color scheme
Issue: Dark gray, green, and default colors are hard to distinguish, making users with visual impairments or different terminal themes struggle to read the chart
Suggestion: Use more distinct colors or add text indicators alongside colors (as mentioned in point 2 above)
4. Confusing legend descriptions
Issue: The legend mixes weekly and hourly concepts inconsistently, making "Default = weekly capacity beyond the hourly window" completely unclear. Additionally, using dark gray for used limits and default for remaining limits feels backward - muted colors should represent unused capacity, not what's already consumed.
Current legend:
- Dark gray = weekly usage so far
- Green = hourly capacity still available
- Default = weekly capacity beyond the hourly window
Suggested legend:
- Default = Used this week
- Magenta = Remaining usage this hour
- Dark gray = Weekly quota remaining
5. Unclear warning message
Current: Hourly usage exceeded 50% of the limit. Run /limits for detailed usage.
Issue: Passive voice, repetition, and unclear call-to-action
Suggestion: You've used 50% of your hourly limit. Run `/limits` for details.
These changes would significantly improve usability for all users, especially those with visual impairments. Thanks for considering this feedback, and let me know if you need any more details!
What is the expected behavior?
No response
What do you see instead?
No response
Additional information
No response
What version of Codex is running?
No response
Which model were you using?
No response
What platform is your computer?
No response
What steps can reproduce the bug?
Overview
The recently merged rate limits display (Tui: Rate limits #3977) has several UX and accessibility issues that make it difficult to read and understand.
Issues Identified
1. Confusing tip text
Current:
Tip: run `/limits` right after Codex replies for freshest numbersIssue: Awkward phrasing and unclear grammar make this hard to parse quickly
Suggestion:
Tip: Run `/limits` after Codex responses for the most current usage data.2. Poor visual chart design
Issue: The ASCII chart using repeated
(>_)logos creates excessive visual noise that makes it difficult to quickly assess usage patternsSuggestion: Consider simpler characters like
█▓░or even just#.for better readability3. Low contrast color scheme
Issue: Dark gray, green, and default colors are hard to distinguish, making users with visual impairments or different terminal themes struggle to read the chart
Suggestion: Use more distinct colors or add text indicators alongside colors (as mentioned in point 2 above)
4. Confusing legend descriptions
Issue: The legend mixes weekly and hourly concepts inconsistently, making "Default = weekly capacity beyond the hourly window" completely unclear. Additionally, using dark gray for used limits and default for remaining limits feels backward - muted colors should represent unused capacity, not what's already consumed.
Current legend:
Suggested legend:
5. Unclear warning message
Current:
Hourly usage exceeded 50% of the limit. Run /limits for detailed usage.Issue: Passive voice, repetition, and unclear call-to-action
Suggestion:
You've used 50% of your hourly limit. Run `/limits` for details.These changes would significantly improve usability for all users, especially those with visual impairments. Thanks for considering this feedback, and let me know if you need any more details!
What is the expected behavior?
No response
What do you see instead?
No response
Additional information
No response