[BUG] config -> usage -> weekly is missing date, has only time
Resolved 💬 3 comments Opened Apr 23, 2026 by memory-thrasher Closed May 8, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
<img width="1886" height="842" alt="Image" src="https://github.com/user-attachments/assets/e3025f91-4116-478c-b03a-b989af0fcf2e" />
weekly is missing date, has only time
What Should Happen?
date and time of usage reset should be visible
Error Messages/Logs
From claude session:
❯ /usage
⎿ Status dialog dismissed
❯ When does the claude weekly allotment of usage reset? It says 5am and 11% used. Yesterday it was 100% used and said 12pm. Since it's explicitly "weekly" usage, it should not reset twice within two days. Yet, it has obviously reset in
the last few hours to be reduced from 100% to 11%. I suspect I am seeing the time when it would reset but not the date and it really means 5am on some future date next week.
● claude-code-guide(Claude Code weekly usage reset)
⎿ Done (15 tool uses · 24.5k tokens · 53s)
(ctrl+o to expand)
● Short answer: your hypothesis is essentially right — the time shown is the time-of-day of the reset, not a reset happening in the next few hours. The date is implicit.
How Claude Code's weekly limit works on subscription plans:
- The weekly window is a rolling 7-day window anchored to your first message of that week. Once it resets, the new window's reset clock is pinned 7 days out from whatever time-of-day that first message landed on.
- /usage displays only the time-of-day for the weekly reset, not the full date. "Resets at 5am" means 5am on the day 7 days after the current week's first use — it does not mean 5am tomorrow.
- Because the anchor moves each week based on when you first use Claude in the new week, the displayed time-of-day shifts week to week. That's why you saw "12pm" last week and "5am" this week: your first message of the new week
happened around 5am, so this week's reset is pinned to 5am seven days from then.
- Going from 100% → 11% confirms the previous week did just roll over. You're now at the start of a fresh weekly bucket.
So: no double-reset, no bug. You're reading the clock time of a future reset, ~7 days out, and the time-of-day re-anchors each week based on your first use.
If you want to confirm the actual date, the Usage page in the Claude Console (platform.claude.com/usage) shows the concrete reset timestamp for your plan.
✻ Cogitated for 1m 26s
❯ The bug is that the date of the reset is not showing on the usage screen. It has in the past. The time is worthless without the date to go with it.
● Agreed — a bare time-of-day with no date is a regression, since the weekly reset is by definition up to 7 days out. Worth filing.
You can report it at https://github.com/anthropics/claude-code/issues — include your CLI version (claude --version), a screenshot of the current /usage output, and note that the weekly reset line previously included the date.
Steps to Reproduce
open claude code cli (on ubuntu) with an account with activity in the last few days
/usage
observe the time of the weekly reset is visible but what day it will reset is unknown. Time is useless without the display.
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
current as of last week, exact version unknown
Claude Code Version
2.1.118 (Claude Code)
Platform
Other
Operating System
Ubuntu/Debian Linux
Terminal/Shell
Other
Additional Information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗