Repository navigation
[Bug]: Usage-limit retry notice omits timezone #23018
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/web
Steps to reproduce
Use a host and phone with a one-hour timezone difference. Reach Claude's session usage limit and view the thread in Android Chrome on the phone.
Actual behavior
The same screen shows:
You've hit your session limit · resets 8:30pm (Europe/Madrid)Usage limit reached. Retry after 19:30.
Both refer to the same reset time, but T3's retry notice has no timezone label, making the difference confusing.
Expected behavior
Include the timezone in the retry notice.
Impact
Minor bug or occasional failure
Version or commit
0.1.2-nightly.20261021.3473 (Linux desktop host). Observed October 21, 2026.
Screenshots
Activity
juliusmarminge commentedon Oct 21, 2026
Reproduced on main 9179178: the retry notice rendered the reset time in the viewer's local format with no zone, so it did not match Claude's zone-labelled reset message when the viewer sits in a different timezone than the host.
Fix in https://git.cafe/pingdotgg/t3code/pulls/23029: the notice now appends the viewer's IANA timezone on web, desktop and mobile, keeping each client's existing time format. A regression test covers changing the device timezone while the app stays open. The timestamp already crosses the wire as an ISO instant, so no server or contract change.