[FEATURE] Status line reset time is ambiguous when past the reset hour

Resolved 💬 2 comments Opened Mar 24, 2026 by roscoekerby Closed Apr 23, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

## Summary
The status line shows "resets 4pm (Africa/Johannesburg)" but doesn't indicate
whether that's today or tomorrow. When the current time is past the reset hour,
this is ambiguous.

<img width="1498" height="769" alt="Image" src="https://github.com/user-attachments/assets/3aeddf87-72d2-4789-bb1c-80aeea1e1b90" />

## Steps to Reproduce

  1. Use Claude Code past the weekly reset time (e.g., it's 7pm and reset is 4pm)
  2. Check the status line — it shows "resets 4pm (Timezone)"

Proposed Solution

Expected Behavior

"resets 4pm tomorrow" or "resets Mon 25 Mar 4pm" when the reset time has
already passed today.

## Actual Behavior
"resets 4pm (Africa/Johannesburg)" — no indication it's the next day.

Alternative Solutions

<img width="1411" height="637" alt="Image" src="https://github.com/user-attachments/assets/3245ba63-03fc-4bc1-bbe7-30480c1826bf" />
Going to web.

Priority

Medium - Would be very helpful

Feature Category

API and model interactions

Use Case Example

The status line shows "resets 4pm (Africa/Johannesburg)" but doesn't indicate
whether that's today or tomorrow. When the current time is past the reset hour,
this is ambiguous.

Use Case Example:

  1. It's 7:27pm (Africa/Johannesburg)
  2. Weekly reset is at 4pm the same timezone
  3. Status line shows "resets 4pm (Africa/Johannesburg)"
  4. User has to mentally check: is it past 4pm? Yes — so that means tomorrow
  5. Should instead show "resets 4pm tomorrow" to remove ambiguity or actual date of reset

Additional Context

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗