[BUG] Usage Reset Not Triggering at Scheduled Time

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?

Summary

Weekly usage limits show a reset time of 10pm (America/Vancouver timezone), but the reset has not occurred even though it's now 11pm local time in the same timezone.

Environment

• Timezone: America/Vancouver (Victoria, BC)
• Current time: 11:00pm (Pacific Time)
• Reported reset time: 10:00pm (America/Vancouver)
• Current usage: 97%
• Claude Code version: Latest

---

Labels: bug, usage-system, timezone

What Should Happen?

Expected Behavior

When the scheduled reset time (10pm America/Vancouver) arrives, weekly usage should reset to 0% and the counter should start fresh.

Actual Behavior

• /usage command shows reset will happen at 10pm (America/Vancouver)
• Current local time is 11:00pm (same timezone)
• Usage remains at 97% with no reset having occurred
• The reset time has passed, but the system has not triggered the reset

Error Messages/Logs

Steps to Reproduce

Steps to Reproduce

1. In America/Vancouver timezone, approach or exceed 10pm local time
2. Run /usage command
3. Observe that reset time is shown as 10pm (correct timezone)
4. Wait until after 10pm local time
5. Run /usage again
6. Observe usage percentage has not reset

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.129 (Claude Code)

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

Possible Causes

• Reset timestamp is calculated incorrectly (off by 1 hour?)
• Reset processing is delayed or failing silently
• Usage display is cached and not reflecting actual server state
• Timezone conversion bug between server and client

Additional Notes

• User is located in Victoria, BC (Pacific Time / America/Vancouver)
• Would be helpful if reset time could be shown in ISO 8601 format with UTC offset for clarity