[Feature] Configurable timezone for displayed timestamps (currently UTC-only)
Resolved 💬 1 comment Opened May 30, 2026 by RobertSheltonJr Closed Jul 2, 2026
Problem
Claude Code Desktop displays timestamps (session list, transcript headers, status line, etc.) in UTC with no way to override. For users not in UTC, this requires constant mental math to figure out when a session ran, when a tool call happened, etc.
Checked the settings reference — there's no timezone, locale, or tz field, and no documented env var (TZ, CLAUDE_TIMEZONE) that Claude Code respects.
Requested
Any one of these would solve it:
- Respect the
TZenv var (POSIX/IANA format, e.g.America/New_York) — Node-native, zero new config surface. - Add a
timezonefield tosettings.json— explicit, discoverable. - Fall back to system timezone by default — what users would naturally expect on a desktop app.
Current Workaround
None. The only mitigation is mental subtraction (UTC−4 for EDT, UTC−5 for EST).
Environment
- Claude Code Desktop on Windows 11
- User timezone: America/New_York (EDT)
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗